On Tue, Jun 17, 2014 at 10:05 AM, David Tardon <dtardon@redhat.com> wrote:
IMHO there are just two alternatives: Either the code is "ours", in
which case it should be an optional component and should only be updated
together with libreoffice. Or it is external, in which case the sources
should not be duplicated in our repo, but the project should be treated
as another one of the dozen extensions we allow to bundle. That means,
download the .oxt during build, unpack it, put it to instdir and be done
with it. (This is directly supported by gbuild, using
gb_ExtensionPackageSet).
FWIW, after reading this thread, I concurs with the above.
The current expressed 'problem' seems a self inflicted wound, due to
wanting to become 'a core part of Libreoffice' while not wanting to
follow the consequences associated with that status.
Norbert
---
Tu ne peux pas avoir le beurre, l'argent du beurre (et la cremiere)
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.