To be fair, I think you need to look at this from their perspective as well.
If you use grub the way Arch ships the package, this issue wouldn’t occur yet some people are trying to place all the blame for this on the Arch team.
The situation is complicated which is why I have been trying to not to assign blame anywhere. It took a lot of things including EOS or the end-user automating grub-mkconfig for it to happen.
So who’s fault is it?
- It is grub’s fault because they made the change(except they never released it)
- It is Arch’s fault because they pulled those commits into their package(except it works if you use the package as they intended)
- It EOS’s fault because we automated
grub-mkconfig(except if you don’t automate that the grub menu won’t get updated when things change)
Ultimately, all this highlights is that something has to change and we need to figure out what that something is.