[arch-general] LibreOffice update
Hello, I want to update my LibreOffice installation but pacman informed me about a conflict with the packages. So, there are libreoffice-still-* packages and there is one libreoffice-fresh package. I want to update to 4.3.x. Why are versions split into two branches and does libreoffice-fresh contain all the LO applications like Writer, Calc, etc.? (There is no libreoffice-fresh-writer or libreoffice-writer package) Thanks Vik
Am Sat, 23 Aug 2014 20:08:31 +0200 schrieb Viktor G <meilenweitvoraus@gmail.com>:
Hello,
I want to update my LibreOffice installation but pacman informed me about a conflict with the packages.
So, there are libreoffice-still-* packages and there is one libreoffice-fresh package.
I want to update to 4.3.x.
Why are versions split into two branches and does libreoffice-fresh contain all the LO applications like Writer, Calc, etc.? (There is no libreoffice-fresh-writer or libreoffice-writer package)
Thanks Vik
pacman -Si 'libreoffice-fresh' will sow you that it provides and includes all LibO core applications. We dropped the app splitting because they are of small size and sometimes upstream broken the dependencies between the parts. So pacman -S libreoffice-fresh is what you want. -Andy
2014-08-23 20:20 GMT+02:00 Andreas Radke <andyrtr@archlinux.org>:
We dropped the app splitting because they are of small size and sometimes upstream broken the dependencies between the parts.
Does this also mean we will stop splitting -still? It is strange to split Still but not Fresh. (I'm all for shipping one large pkg by the way) Thanks, Sebastiaan
Am Sat, 23 Aug 2014 20:32:42 +0200 schrieb Sebastiaan Lokhorst <sebastiaanlokhorst@gmail.com>:
2014-08-23 20:20 GMT+02:00 Andreas Radke <andyrtr@archlinux.org>:
We dropped the app splitting because they are of small size and sometimes upstream broken the dependencies between the parts.
Does this also mean we will stop splitting -still? It is strange to split Still but not Fresh. (I'm all for shipping one large pkg by the way)
Thanks, Sebastiaan
Development happens in the fresh packages. All changes will move over to the still package when a new major fresh release happens. Then the massive splitting will be dropped. -Andy
2014-08-23 21:30 GMT+02:00 Andreas Radke <andyrtr@archlinux.org>:
Am Sat, 23 Aug 2014 20:32:42 +0200 schrieb Sebastiaan Lokhorst <sebastiaanlokhorst@gmail.com>:
2014-08-23 20:20 GMT+02:00 Andreas Radke <andyrtr@archlinux.org>:
We dropped the app splitting because they are of small size and sometimes upstream broken the dependencies between the parts.
Does this also mean we will stop splitting -still? It is strange to split Still but not Fresh. (I'm all for shipping one large pkg by the way)
Thanks, Sebastiaan
Development happens in the fresh packages. All changes will move over to the still package when a new major fresh release happens. Then the massive splitting will be dropped.
-Andy
Ah, that makes sense. Thanks for clearing it up! Sebastiaan
Thanks for your fast replies! You're a very good community and I'm happy to use this system. :) -- Vik 2014-08-23 21:44 GMT+02:00 Sebastiaan Lokhorst <sebastiaanlokhorst@gmail.com>:
2014-08-23 21:30 GMT+02:00 Andreas Radke <andyrtr@archlinux.org>:
Am Sat, 23 Aug 2014 20:32:42 +0200 schrieb Sebastiaan Lokhorst <sebastiaanlokhorst@gmail.com>:
2014-08-23 20:20 GMT+02:00 Andreas Radke <andyrtr@archlinux.org>:
We dropped the app splitting because they are of small size and sometimes upstream broken the dependencies between the parts.
Does this also mean we will stop splitting -still? It is strange to split Still but not Fresh. (I'm all for shipping one large pkg by the way)
Thanks, Sebastiaan
Development happens in the fresh packages. All changes will move over to the still package when a new major fresh release happens. Then the massive splitting will be dropped.
-Andy
Ah, that makes sense. Thanks for clearing it up!
Sebastiaan
participants (3)
-
Andreas Radke
-
Sebastiaan Lokhorst
-
Viktor G