On Sun, Oct 11, 2020 at 07:47:22AM +0200, Christopher Engelhard wrote:
Hi,
the nextcloud server package is currently stuck at ancient version 10
(current is 20) in EPEL7 (It's not (yet) available EPEL8 repos).
I'd like to fix that, but
- upstream releases a new version roughly every 4 months
- they support them only for roughly 1 year (officially it's "at least 8
months")
- nextcloud receives A LOT of bug- and CVE-fixes, and there is no way
I'll be able to backport all of those, so staying on an older version
after upstream stopped support is not really an option.
So, should this still be in EPEL even though it would receive major
version updates or is it better to retire it from EPEL?
I suspect that EPEL users would probably prefer to run it from
upstream's containers anyways, so retiring might make more sense, but
I'm open either way.
There's a number of options:
* Keep in epel - As you note though this is major upgrades and it's not
something people expect.
* It doesn't help you any with epel7, but for 8 you could put it in
epel8-playground. There's much more expectation of packages that have
major upgrades and change things, so people who consume it might be fine
with that.
* You could try a module (again does not help with epel7). This should
work except if you need any non default modules.
* You could just put it in a copr (this would work for both epel7 and
epel8). It's not as discoverable there, but this might be a good
solution.
kevin