Re: [tdf-discuss] Linux distros and LibO packaging
Il 09/01/2011 16:56, RGB ES ha scritto:
Good idea! Maybe a wiki page will be enough, but someone from each
distro with enough knowledge should fill their part.
On my experience, when giving support to OOo users on Linux many of
their problems came from distro patches and were not present on
vanilla build (anyone remember when kde4 integration appeared on
openSUSE, offering to their users 0 KiB .doc files?).
Or the long awaited pdf export xref bug
Or the recent OpenSuSE build Libò bug
On both I tried helping to solve problems.
2011/1/9 Jean-Baptiste Faure<firstname.lastname@example.org>:
I think that we should have a webpage where Linux distributions who are
packaging LibO, could list what changes they made compared to the
"official" build by TDF.
I see two main advantages :
- for users and helpers : they will know easier if a problem comes from
LibO or from packaging
- for QA : it will be easier to know if a test done, for example on a
version from Ubuntu PPA, may be consider as valid or not for LibO from a
general point of view.
Last but not least, that will increase transparency : we will know what
we are talking about when we will talk about LibreOffice. ;-)
So, is it a good idea to ask the Linux distributions to publish the
changes they made to the official build ?
Seuls des formats ouverts peuvent assurer la pérennité de vos documents.
Unsubscribe instructions: E-mail to email@example.com
*** All posts to this list are publicly archived for eternity ***
Impressum (Legal Info)
: 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