Bug 644878

Summary:	app-office/libreoffice-5.3.7 ebuild request
Product:	Gentoo Linux	Reporter:	Andrey Aleksandrovich <andrey.aleksandrovich>
Component:	New packages	Assignee:	Gentoo Office Team <office>
Status:	RESOLVED OBSOLETE
Severity:	enhancement	CC:	jstein
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=908468
Whiteboard:
Package list:		Runtime testing required:	---

Description Andrey Aleksandrovich 2018-01-17 19:00:34 UTC

The Official LO site provides two branches 'fresh' and 'still' for download.
Fresh = If you're a technology enthusiast, early adopter or power user, this version is for you!
Still = If you deploy LibreOffice in an enterprise or corporate environment or are a conservative user, please choose this version.
As for now, fresh is 5.4.4, and still is 5.3.7

But portage now has only 5.4* versions of LO, 5.3* is already removed (prematurely).
So, as a conservative user I think, we need 'still' versions in the portage.

Reproducible: Always

Comment 1 Andreas Sturmlechner gentoo-dev

2018-01-17 19:06:14 UTC

Do you have any issues with LO-5.4? LO-5.3.7 was never stabilised in Gentoo and it would be a waste of time as we are close to 5.4.4.2 stable.

Comment 2 Andreas Sturmlechner gentoo-dev

2018-01-17 19:07:07 UTC

* while 6.0 is imminent, which will make 5.4 the new 'still' series.

Comment 3 Andrey Aleksandrovich 2018-01-18 15:10:20 UTC

(In reply to Andreas Sturmlechner from comment #2)
> * while 6.0 is imminent, which will make 5.4 the new 'still' series.

Oh, 2 weeks... and 6.0 will be released. All right, in this case, it is good to wait new 'still' and switch to it. But for the future, please, keep both series available in portage.

Comment 4 Andreas Sturmlechner gentoo-dev

2018-01-18 20:07:47 UTC

We don't really follow upstream's recommendations there. Unless there is a compelling reason to keep an old branch, like a serious defect in the following versions, it is dropped after stabilisation of the new one. LibreOffice has a lot of accompanying libraries it depends on, many of which are breaking compatibility each time, and as soon as a newer version is stable, keeping the old one running (including the older dependencies it requires) becomes a nuisance. And since manpower is limited, no one is there to take care (test) of an old-LO bump after the fact - as you know, it is a rather big package to build. Right now, 5.4 already (and even 6.0) needs a backported patch to build against a newer library version that is being stabilised for security reasons, and 5.3 would need the same work plus potentially more.