Comment # 3 on bug 1006409 from Stefan Hundhammer

This has always been a side effect of the very concept of patterns: They are
really just a bunch of dependencies. But the same package might be required by
one or more patterns, and also by other packages. That makes removing them
difficult.

If you are in that kind of situation, your only chance is to switch to the
patterns view in the *detailed* software selection where you can see all the
packages that constitute a pattern individually, and then trying to remove them
one by one.

Yes, that is tedious. You will have to make many individual decisions, and that
makes it very error-prone. There is no reasonably easy way to do this.


And this is now 6 years old without any action. That means that nobody found
this important enough during all that time to invest any development resources,
even if somebody would have had a good idea how to do this. Realistically, this
will not change for the forseeable future.

Closing.