Especially because there is no way to limit the packages installed from a PPA AFAIK. If the PPA has a “new” version of NGINX, or of libc, or of Wayland - you get it, too!!!
Absolutely. Ideally you should have zero PPAs. There’s definitely a cost for using this feature. Most commonly it comes in the form of instability when you end up with incompatible or broken packages because the maintainer wasn’t playing an active enough role. YMMV!
The company I work for has a apt repo that both has some tools I like to install, but also maintains super new versions of certain libraries and kernels with configs that would break my laptop.
So I have the priority set low enough that if a package exists in any other repo it it preferred over my companies version.
Also sorry for the slow reply I forgot to check my messages 😄
Especially because there is no way to limit the packages installed from a PPA AFAIK. If the PPA has a “new” version of NGINX, or of libc, or of Wayland - you get it, too!!!
Absolutely. Ideally you should have zero PPAs. There’s definitely a cost for using this feature. Most commonly it comes in the form of instability when you end up with incompatible or broken packages because the maintainer wasn’t playing an active enough role. YMMV!
You can set packages from a particular repo to a lower priority so that they are only installed when you expressly ask for them
How does one do that, Wise Zorro?
https://wiki.debian.org/AptConfiguration#Using_pinning
The company I work for has a apt repo that both has some tools I like to install, but also maintains super new versions of certain libraries and kernels with configs that would break my laptop.
So I have the priority set low enough that if a package exists in any other repo it it preferred over my companies version.
Also sorry for the slow reply I forgot to check my messages 😄
No worries, been there! And thank you very much, it will save me tons of time sifting through updates on the VMs that need PPAs!