How do non explicitly installed package dependencies get updated in Arch? Do they update independently of the package that is dependent on them, or do they get updated when the parent package updates? Or is it some secret third thing?
Thanks!
You must log in or register to comment.
Every package gets updated, when there is an update for it. Dependencies don’t matter for that.
Only if a package depends on a specific version of another package, is there a difference. When the dependency would get updated to a version that doesn’t satisfy the version requirement. Then an error gets thrown and nothing gets updated.
But the package maintainers for the official repos don’t really let that happen. It’s more of a problem with aur packages.
Adding to this: individual package updates are not supported. Always update your whole system, unless you know what you are doing.
Thank you! Everything I wanted to know, and little bit extra :)
Are you talking about package dependencies that were pulled in after compiling a package from AUR ? As far as I know (I’m not much of an AUR user, except when I quickly want to test some software. Please correct me if I’m wrong) if you normally would run
sudo pacman -Syuyou can instead of that runsudo yay -Syu(or other AUR helpers that support this) which would update both Arch packages and these from AUR.In my experience, it’s idependently unless updating breaks a version dependency on another package. In that case pacman won’t update anything until the issue is resolved. I think I’ve only ever had this happen with AUR packages.
Fairly certain it’s the first unless you’re forcing an update on some dependency with pacman. If I’m wrong, I’m more likely to get corrected than you are to get an answer and we will both learn something lol.
