Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index


On Tue, Mar 06, 2018 at 12:13:11PM -0300, Olivier Hallot wrote:
I really need advise and help to proceed and build the necessary
packages to replace the old help.

It requires understanding of build process, makefiles and perl scripts
in scp2/ module.

The task looks simple: once the new help is built (--with-help=html),
the help files are available in core/instdir/help/6.1 so it must take
the 6.1/ folder and make a package, which is as simple as zipping it. Of
course, replace '6.1' by %PRODUCTVERSION.

https://bugs.documentfoundation.org/show_bug.cgi?id=116240
https://bugs.documentfoundation.org/show_bug.cgi?id=115312

Any collaboration or help here is welcome. Question on the task here or
in #libreoffice-dev

Forgive my ignorance, maybe I am missing something - but if you did the scp2
stuff correctly (and defined the gid_*s correctly) the packaging should just
pick it up? I mean, there's already help packaging doing that packing up
the old help.

So it basically only boils down to scp2.

How did the stuff end up in instdir anyway? With scp2? Or via some
manual hackery?

That would also solve it automatically for distributions who use
make disto-pack-install (which is basically a make install with writing
the contents of the gid_*s to gid_* files on disk so one can use those
for splitting the packages appropriately)

Regards,

Rene

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.