Some of us work on other opensource projects on our Mac machines which
happen to need MacPorts or HomeBrew.
Having LibreOffice simply say "I refuse to build on this machine because
you've already installed some other stuff" is not very friendly.
But neither is it very useful to have the already small set of OS X -based
developers split into those who use a pure upstream way to build, those who
use HomeBrew libjpeg but bundled Python, those who use MacPorts Python and
libjpeg, etc. For each, normally bundled, external software package, that
could optionally be used from either MacPorts or HomeBrew, the
configuration space grows threefold in size. How hard can it be to make
sure to drop some entries from PATH in the shells where one works on
LibreOffice?
--tml
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.