On Wed, Oct 04, Richard Biener wrote:
On Wed, 4 Oct 2023, Thorsten Kukuk wrote:
On Wed, Oct 04, Richard Biener wrote:
Were other alternatives to solve the transactional update issue considered, like placing /var/lib/alternatives in /run/ and populating that via some (systemd?) service at boot time from configuration?
This files are not owned by a RPM and need to survive a reboot. Beside that, /run/ would not solve any of the current problems with update-alternatives.
Since /run isn't persistent it solves the transactional revert restoring the reverted distribution provided config like libalternatives does.
/var/lib/alternatives contains data update-alternatives creates during installation of packages using update-alternatives. So if you reboot, this informations are lost, but never rolled back.
How does libalternatives solve the issue that its configuration is by definition not restored by rollback either? It only works to roll back when there's no configuration change inbetween?
??? Since libalternatives uses the standard configuration locations and has a clean split between distributon provided configurations and admin made changes, the configuration is of course restored during a rollback.
It rolls back the admin made changes?!
Of course. If you do a rollback, you want a consistent, known working system again. Which means, admin made config changes, which may not fit anymore and may disrupt the system, are not wanted and needs to be rolled back, too. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)