manjaro-settings-manager needs an update. It does not show the 6.13 kernel as being EOL.
Why does the entire application need updating everytime a kernel goes EOL or a new one added? Surely that’s a data thing.
1 Like
I’m not sure. I don’t know how it works, really — I don’t even have it installed anymore. But it’s the same thing whenever upstream designates a new kernel as LTS. 
1 Like
I guess adding a function to interrogate an external source for some info is unreliable and may cause multiple sorts of breakage depending on the type of response or no response from the external source (and support for this various possible breakage cases should be implemented too), compared to having the information hardcoded in the program which probably simplifies a lot the programming. It is easy to do it this way I would guess.
1 Like
Mmmm, perhaps @philm can tell us.
Nevertheless this could be handled better from a distro point of view: the data should be split into an extra package (e.g. manjaro-settings-manager-data) which manjaro-settings-manager has as a hard dependency.
Only the manjaro-settings-manager-data package would need updates when kernels go EOL (that burden would still not go away) but the application itself wouldn’t need rebuilding every time.
5 Likes
And for good measure — because I’ve noticed some issues in this regard with some of the Manjaro tools (and even with some Arch tools) — this data file should then be located under /var/lib somewhere, as opposed to under /usr.
/usr is to be regarded as read-only, because it holds virtually all of the system’s binaries — /opt contains binaries too and should also be regarded as read-only, but /opt is normally for applications that rely on their own installers instead of on the system’s package manager, as for instance if you install firefox directly from Mozilla’s website.
Some of the packages we inherit from Arch — and some from the AUR — however violate this principle. They rely on the system’s package manager and install part of their binaries under /usr, while at the same time also parking other files under /opt.
But in any case, those are then either way not data files. A file with information on which kernels are current, which are LTS, and which are EOL does not belong under either /usr or /opt. It should go under /var/lib. 
Change to a branch where the Kernel is actually removed from the repos …
2 Likes
Oh, but it’s not my problem. I only run LTS kernels, and I don’t even have manjaro-settings-manager installed anymore — not even mhwd, for that matter.
There are however members who wonder why MSM isn’t showing 6.13 as an EOL kernel, and then what do we have to tell them, other than that MSM is not actively being maintained?