Date: prev next · Thread: first prev next last


On Thu, Oct 10, 2013 at 05:09:34PM +0100, Michael Meeks wrote:
* Bundled extensions (Stephan)

So, some extra thoughts / suggestions for that:

There are two categories of extensions:

1. "Internal" extensions. These are built from sources and include
   presentation-minimizer, nlpsolver, wiki-publisher and
   mysql-connector-ooo. I think it should be easy to add a
   GeneratedPackage into the Extension gbuild class that copies the
   extension root dir from workdir to the right place in instdir. (The
   .oxt file will still be produced and copied to solver, but I do not
   think this is worth any more effort. Much better way to spend one's
   time would be to convert these extensions to optional components.)

   I will look into this tomorrow.

2. "External" extensions. These are merely copied to solver from
   $TARBALL_LOCATION (in extras/ It would be very
   easy to unpack them and copy them to instdir instead (i.e., what is
   needed is to create an UnpackedTarball and ExternalPackage for every
   one of them and change ARCHIVE for FILELIST in scp2). There is 14 of
   these extensions in extras, plus ct2n which is already repacked
   during build. If this is agreed upon, I suggest to move the makefiles
   to a new module, e.g., extensions, as extras is cluttered enough

   This would be very suitable for an easy hack.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.