On 10/10/13 09:14, Stephan Bergmann wrote:
....which brings me back to my original question for a universal trigger
whether or not to produce installation sets during a build.
Seeing that --enable-epm currently effectively fulfills that role
everywhere but on Windows, one option would be to make it fulfill that
role on Windows too. (I have a local patch to do that.)
The alternative would be to introduce an explicit
--enable-installation-sets. Opinions, anyone?
we already have --with-package-format, much simpler to do nothing if the
user doesn't specify that than adding another option, or using
--enable-epm on a plaform where EPM is irrelevant.
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.