On Tue, Dec 24, 2013 at 11:33:24AM +0000, Michael Meeks wrote:
I'm not that clear on what you suggest. I assume you are not suggesting
doubling the number of Linux packages to 4x per architecture: .deb
+ .rpm (old) and .deb + .rpm (new) - and then more fooling in the
downloader etc. ? (that doesn't sound sensible for a minority platform -
with x86_64 -> 8x package archives.
No, I dont want to suggest to get even more packages. Rather to build the core
(non-kde/gtk-stuff) of LibreOffice on the 'old' baseline, and then have a
chroot on that same machine with a newer baseline, and build just the kde/gtk
parts against that baseline and the already partial build tree we have from the
build on the old baseline. So you would end up with one set of .rpm/.debs,
where the core of it runs anywhere, while the gtk/kde bits require something
halfway recent.
But in the end its probably not worth it at all, if we just make sure distros
can be very quick with their packages, so that upstream binaries are just used
as a 'proof it build'. ;)
Best,
Bjoern
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.