![](https://seccdn.libravatar.org/avatar/ba6138f793e72be6644854fdc3ec2f02.jpg?s=120&d=mm&r=g)
Hello, On 2022-05-24 13:35, Simon Lees wrote:
On 5/24/22 20:41, Johannes Meixner wrote:
In contrast if a WiFi pattern was used "in between" the automatism may only request to install this pattern but the user could simply "taboo" this one pattern instead of "tabooing" a list of various individual packages which may change over time.
It doesn't work like this as patterns only Require or Recommend other software they don't Provide anything, so all you achieve by "tabooing" a pattern is that pattern won't be installed, if I had a wifi pattern "tabooed" it would not prevent NetworkManager-Wifi from being installed.
Sigh :-( The more I learn about package dependencies the more I come to the conclusion that it could be impossible to use them to let the user choose what software is wanted or unwanted. Perhaps only hard dependencies do actually work but weak dependencies are in the end a dead end? Perhaps weak dependencies do not actually solve something but only mitigate/hide certain issues for average users while causing other problems for other users? Kind Regards Johannes Meixner -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 - 90409 Nuernberg - Germany GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman (HRB 36809, AG Nuernberg)