You're viewing part of a thread.
Maybe because the jre thing was an update that required manual intervention, there was an Arch news item about it. You're expected to read the Arch news before an update when you're running Arch. This can be automated with
alias update='yay -Pw && pacman -syu'If that's too much for you, use a different distro.To make it even more convenient, register to their mailing list and you get a heads up.
My ADHD and 1297 unread emails make that a bad idea.
With the alias, the news pop up in front of me right when they're relevant.Those are rookie numbers son, you gotta get on that.
You ppl don't use auto archive/categorise/delete ?
Why can't it print into as part of the update? Why is it a separate command?
It's the KISS philosophy. The package manager is for managing packages, not for reading mail
I've seen this a few times with various distributions. People always say stuff about checking news files or whatever their distros call them. I have no idea what those are or where to find them. It would seem extremely prudent for the update tool to print relevant information.
Brew does this. (I am not using Brew as an example of a perfect package management tool.) It also has "caveats" that get printed for some packages. It seems much more useful this way.
Printing the entire change log is overkill, but at least breaking changes and such would be extremely useful.
I just went "Shiit! Am I sitting on potential system breakage?" (because I don't remember doing any such intervention)
But turns out it was just a conflicts with change.From what I know,
pacmanstraight-up asks you what you want, in these cases. Sure, it's technically manual intervention, but for me, who scans over updated packages every-time, this is considered standard procedure.Manual intervention is when GRUB doesn't install properly using the suggested command and you have to learn where your distro places the boot image and configure stuff accordingly.
Also, I don't have JDK so...