Hi,
the LibreOffice build uses EPM ("ESP Package Manager"), e.g. to generate
deb packages when the build option "--with-package-format=deb" is given.
I realized that LibreOffice uses and old version of EPM and applies a
patch that does quite a few modifications [1].
As I experienced a build failure when using unpatched upstream versions
of EPM (i.e. no build option "--with-epm=internal" given), I was
wondering whether it wouldn't be a good idea to work on integrating
(still relevant) LibreOffice modifications upstream? [2]
I would be willing to at least look at those things I come across while
trying to build the Debian packages with upstream EPM.
What do you think?
What would be needed to make sure that proper attribution for the
modifications is made? (E.g. is it enough to mention something like
"This commit is based on a patch of the the LibreOffice community to an
older version of EPM." or something like that?)
Best regards,
  Michael
[1] Patch: file "./external/epm/epm-3.7.patch" in the "core" git repo
[2] upstream GitHub page: https://github.com/michaelrsweet/epm
Context
- Bringing LibreOffice modifications for EPM upstream? · Michael Weghorn
 
  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.