[aur-general] moving libpaper to extra / new (Calligra/LibO) Office related libs
I'd like to make use of libpaper in Ghostscript, Cups and LibreOffice. So I will move it to extra and will maintain it there. Also I was told that Callibre can make use of certain libraries in future versions that are already part of the internal LibreOffice sources. I will do some investigation and will decide if we make them system libs so we can do shared linking to these libs. Please have a look at the PKGBUILD, what internal sources we will use in LibO 4.2 : https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD.42?... -Andy
On 01/22/14 at 08:54am, Andreas Radke wrote:
I'd like to make use of libpaper in Ghostscript, Cups and LibreOffice. So I will move it to extra and will maintain it there.
Also I was told that Callibre can make use of certain libraries in future versions that are already part of the internal LibreOffice sources. I will do some investigation and will decide if we make them system libs so we can do shared linking to these libs.
Please have a look at the PKGBUILD, what internal sources we will use in LibO 4.2 :
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD.42?...
-Andy
It totally makes sense to create packages for libraries which are used in Calligra and LibreOffice. Creating packages for obscure libraries used only in LibreOffice seems like an unnecessary maintain burden, I just wonder why you don't use boost and rhino from our repos. When I used to contribute to LibreOffice, I've build flawlessly against our repo's boost version. -- Jelle van der Waa
On Jan 22, 2014 2:03 PM, "Jelle van der Waa"
On 01/22/14 at 08:54am, Andreas Radke wrote:
I'd like to make use of libpaper in Ghostscript, Cups and LibreOffice. So I will move it to extra and will maintain it there.
Also I was told that Callibre can make use of certain libraries in future versions that are already part of the internal LibreOffice sources. I will do some investigation and will decide if we make them system libs so we can do shared linking to these libs.
Please have a look at the PKGBUILD, what internal sources we will use in LibO 4.2 :
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD.42?...
-Andy
It totally makes sense to create packages for libraries which are used in Calligra and LibreOffice. Creating packages for obscure libraries used only in LibreOffice seems like an unnecessary maintain burden, I just wonder why you don't use boost and rhino from our repos.
When I used to contribute to LibreOffice, I've build flawlessly against our repo's boost version.
-- Jelle van der Waa
I have to agree with this. My two cents would be on the basis of organization and consistency throughout the repository, although I'm likely underinformed.
Am Wed, 22 Jan 2014 21:03:14 +0100
schrieb Jelle van der Waa
It totally makes sense to create packages for libraries which are used in Calligra and LibreOffice. Creating packages for obscure libraries used only in LibreOffice seems like an unnecessary maintain burden, I just wonder why you don't use boost and rhino from our repos.
When I used to contribute to LibreOffice, I've build flawlessly against our repo's boost version.
Libpaper is now used by cups and ghostscript. Libvisio is now used by Calligra and system libvisio will soon replace the internal libvisio in LibO. Libetonyek and libodfgen are used in LibO and will be used in Calligra 2.8.x. - so packaging these libs also makes sense. Boost is only a makedep in LibO and not linked. Build was very often broken when we had updated our system boost. As it has no benefit at runtime I stay with the well tested internal boost in LibO. For rhino LibO uses a patched source. I doubt we can use our rhino pkg. Have a look at http://cgit.freedesktop.org/libreoffice/core/tree/external/rhino/README -Andy
participants (3)
-
Andreas Radke
-
Jelle van der Waa
-
Tanner Danzey