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


Hi,

On Sat, Jan 29, 2011 at 04:59:27PM +0100, Rene Engelhard wrote:
On Sat, Jan 29, 2011 at 08:36:35AM -0700, Tor Lillqvist wrote:
it ships own copies of dozens of standard 3rd-party packages,

"standard" from the viewpoint of up-to-date Linux distros, that is. Don't forget that 
LibreOffice is supposed to run also on not-so-up-to-date Linux installations. (As far as I 
know, the generic Linux build of LibreOffice is, or am I confusing with go-oo times?)

Nah, there's also various internal libs so old that they were even outdated
years ago (zlib for example)

sent to early. I also wanted to mention what consequences this can have:

*ANY* upload to Debian containing a internal zlib will be automatically rejected. And
TTBOMK there's no way to get anything with internal zlib into Debian as the error
is not overridable.

And that#s pure because zlib gets security issues often - and you wouldn't want to touch
all packages using zlib. The same argument applies to all of the other libraries, too.
3.3.0 picked up libxml2 and xpdf (using xpdf is a bug anyway, poppler should be used) fixes
for internal libraries...

Grüße/Regards,
 
René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  rene@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70

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.