Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi,

people ask me about the libreoffice/build repository. The status is that
it is not officially supported in the libreoffice-3-4 branch and master.
We need to migrate all the common stuff into bootstrap and other
repositories. The distro-specific hacks should be moved to the local
scripts, .e.g. spec files.

The current state is that about 50 patches are applied for
--with-distro=SUSE:

     + 20 patches are for mono; I think that we could release 3.4
        without them
     + 6 patches are for PostgreSQL driver; we should integrate them
       into the extensions repository and make the build optional
     + system-python-uno-path.diff: need a clean solution before tit
       get's integrated
     + split-icons-search-usr-share.diff, sfx-check-real-help-path.diff:
       needed only when you put icons and help in /usr/share
     + the rest is a controversial stuff that is not really needed or is
       needed only for SUSE

I would like to migrate some of the helper scripts that helps with
packaging, .e.g desktop integration (wrappers, icons, man pages),
filelist filtering.

We do not plan to migrate the patches and patch-apply script. It is easy
to commit changes into the official sources, so we do not need any
complex framework for applying extra patches.

Any help with the migration is welcome.


Best Regards,
Petr


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.