Every now and then, the updating process under Manjaro requires some „special care“ in form of the strong recommendation to do the update in a terminal or on a tty or to include an automatic downgrade switch.
I know, it‘s not that often, but if it happens, quite some users get bitten. Yes, you may say Arch-based and rolling isn‘t easy street and that users should get acquainted to first read the announcement and then update and you will be mostly right. Alas, there is a gripe: Manjaro aims to be user friendly. And it does great things to be user friendly (it has unstable, testing and stable branches, it has really nice GUI package managers, it has a kernel manager, so many nice, user friendly things …). But if we are realistic, the tools available for updating tempt users to use them and in the forum we are constantly praying that a safe update goes over the terminal with
sudo pacman -Syyu only that this time exactly this routine would extraordinarily have broken many systems, because
sudo pacman -Syyuu would have been needed.
So while trying to keep the recent discussion on one of the recent stable updates productive (and not really succeeding in that) here is a suggestion that could be considered: to separate the general package install routines (Octopi, pamac) and the updating process and to implement an update manager.
White-paper for an update manager:
What it should do:
Notify the user that a new update is available.
Warn whether any special care is required to have a sane update. In principle this could just mean to throw the warnings of the forum announcement at the head of the user (whether he has an account or not).
Present a shortcut or link to perform the update.
How it could be implemented (beware, I’m not a programmer):
a) through a dedicated RSS feed, or
b) similar to what the kernel manager already does
c) from scratch with notification access and indicator etc …
d) $insert smart suggestions from more capable folks
One idea may be to “automatically” implement for extra-ordinary update procedures may be to have a Manjaro-version package, that (i) counts up the version (e.g. by date 2019-01-25) and (ii) pulls in required dependencies and that (iii) notifies the update manager that a system update is available.
I think the manjaro-system package could be used or extended for this?
The main point would be to prevent the GUI package managers to indicate and perform system updates and to inform the user by other means that an update is available. I guess it would be OK to teach users to go in a terminal for updating procedures even if it feels less user-friendly. Or, the update-manager just presents a link to a script that then fires up a terminal and does the updating “magic” (incl. asking for the password).
What it is for:
Improve user-friendliness by avoiding hazardous update procedures.