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


Hi,

On Sun, Jan 23, 2011 at 07:13:56PM +0100, Andrea Pescetti wrote:
Rene Engelhard wrote:
On Wed, Jan 19, 2011 at 11:13:48AM +0100, Rene Engelhard wrote:
Besides that, distros will have to continue libreoffice-build, which does
still contain patches. (Removing those would be a big regression about
what we ship right now)

Thanks. So some distributions will still need to patch LibreOffice
because the "vanilla" LibreOffice would be a regression for their users
with respect to the current OpenOffice.org/Go-OO/LibreOffice they ship.

Yep.

This, together with issues like the weird problem you linked to
https://bugs.freedesktop.org/show_bug.cgi?id=31271
indeed qualify as "compelling arguments" for distributions needing to
patch LibreOffice much like they do with OpenOffice.org (even though of

not as much, as getting fixes or other stuff into the main codebase is far
better in LibO than it was in OOo where it was extremely difficult.

course in some cases the patches will be temporary fixes that will
eventually get merged in the main codebase).

Yep. And most of the go-oo fixes are already in the stock LibO anyway, so
nothing to big here either.

Grüße/Regards,

René

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***

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.