Hi Michael,
So I should create option like --enable-oxygenoffice, and add my stuffs
here? All things depending in the code directly? How should I make the
download conditional? I really don't want to enforce anybody to download our
extra stuffs, extensions, etc without using --enable-extra-gallery,
--enable-extra-template,
--enable-extra-sample, --enable-extra-font and all --with-ext-*
(extension) switches.
Best regards,
KAMI
2011/4/19 Michael Meeks <michael.meeks@novell.com>
Hi Kami,
On Mon, 2011-04-18 at 10:33 +0200, KAMI911 KAMI911 wrote:
I recently build a new version from libreoffice-3-4. I found that it
does not not support:
* patches/dev300 infrastructure to patch the source
Right :-)
* download infrastructure for additional stuffs
Oh ? surely we have that with ooo.lst ?
Are we planning this features for bootstrap repo? Or this only for
build repo?
I think the idea is to try to get all of these patches turned into
build conditionals - so we have a single build that auto-adapts to the
underlying system, and has features that can be enabled as required.
Of course, the flip side of that is - we need things flattening and
conditionalizing, and fixing in the bootstrap (and other) repos - rather
than continuing to pile them up inside 'build'.
I guess for 3.4 'build' may still be workable, but I'd like to
completely kill it on master (personally).
Does that make sense ?
ATB,
Michael.
--
michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot
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.