Hi,
I was lately wondering why all the new features / dependencies are
handled as required unconditionaly.
Would it not be possible to add specific with/without switches for
features that require 3rd party libs?
Like cups/cmis/visio/wpd/... so users could choose which features they
really want in during the compile, making the build smaller if they
want to.
I am not saying that we are to backport all the switches right away,
but with disappearance of --with-cmis it occured to me that we add
even new libraries as hard dependencies.
I also know that you can say that we can unbundle this on runtime, but
then again I am gentoo dev so we need this kind of optionality on
build time, and I bet we are not the only ones.
Of course all the switches would be in enabled state by default. If
you are afraid of breakages that would not be noticed i can quite
ensure you that I am capable of running tests for on/off for each
swich weekly.
Cheers
Tom
Context
- [Libreoffice] [RFC] hard dependencies on 3rd party libraries · Tomáš Chvátal
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.