-
Notifications
You must be signed in to change notification settings - Fork 7
Description
It's hard to stay away from installing AUR packages or using an AUR helper like yay when using Arch-based systems. When using an AUR helper, it also manages everything that pacman does. So it doesn't make a whole lot of sense to not be able to disable pacman and just use the AUR helper to do everything especially when they can cross wires with each other which could cause all sorts of mayhem during updates. On top of that, user feedback ( #18 ) tells me that in other distros, there are reasons to disable the native package manager. So who am I to say you can't disable your native package manager if you really wanted to do so no matter what that reason is?
As such, starting in v0.26, Linux users will be able to disable their native package managers. Also, I noticed that there seems to be a growing preference for paru over yay. So I will be adding paru as a "supported package manager". Furthermore, in Arch based distros, if pacman is disabled and yay or paru is enabled, it will default to using the enabled AUR helper by default when you don't specify a package manager in the command (ie. app update which is normally the same as app -m pacman update).
Stay tuned!
What about Mac and FreeBSD?
Well, I don't see it being worth the effort to add native package manager enable/disable functionality to Mac and FreeBSD because there's pretty much only one package manager that app manages respectively so there seems to be no point to disable/enable them. Instead, you just either use app or you don't.
I am open to hearing arguments against this sentiment though and I can potentially fit this in in the future if it in fact becomes a thing.