Would you then have any idea if this would cause a lot of devoted dev tim
e,
part-time, full-time attention. Would LibO then have to have a dedicated
dev
in charge of this?
Marc
I doubt it would require a full-time developer, since changes would
only need to be made when a new version of openoffice or, maybe, when
a new version of a distribution is released, so probably 4 or 5 times
a year. I don't know about deb files, but spec files for rpms would
only require the version number be changed and, if there are changes
to the file names in output, some changes to the list of files. We
are probably talking a few hundred lines of code for the entire spec
file, and only between 1 and maybe a few dozen would have to be
changed for a openoffice update, while only at most 5 or so would
likely need to be changed for a new distribution release (ideally none
would have to be changed in that case).
However, it may still be too much work given the benefit.
Distributions will normally handle the packaging themselves anyway, so
I am not exactly clear on what benefit there would be in duplicating
this effort. Really the main benefit I can see is not to users
directly, it is making sure the software builds on common Linux
distributions without distributions having to make their own
modifications. So it may be worthwhile from a debugging perspective
alone, and if the packages are going to be built then publishing them
would be no added effort.
-Todd
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.