On Wed, Jun 02, 2021 at 10:21:43AM +0200, Sasi Olin wrote:
On Wed, Jun 2 2021 at 09:40:40 +0200, Adam Majer email@example.com wrote:
The third issue is packaging this mess. How many times have any of you made an error with update-alternatives that then broke an update and became almost impossible to fix without further scriptlet hacks? It's fragile, to say the least. The system is also changed during installation and not at runtime -- this makes it potentially inconsistent between snapshots.
It was suggested to handle this as an abstraction in rpm specs, with update-alternatives being handled with rpmdb, which is probably the method I would like the most https://github.com/rpm-software-management/rpm/issues/993
Scriplets are an awful way to deal with this, I agree, but I think managing this through rpm is a better way to go
Yes, this is a way of avoiding the scriptlet issue but it doesn't address other issues. The issue with inconsistent snapshots remains especially for transactional updates.
It's a little funny how update-alternatives became entrenched and how many packages are using it now.