Feature changed by: Ludwig Nussel (lnussel) Feature #309385, revision 42 Title: Improve "Pattern" handling openSUSE-11.3: Rejected by Andreas Jaeger (a_jaeger) reject date: 2013-08-09 13:10:33 reject reason: Not done for 11.3. Priority Requester: Important - openSUSE Distribution: Unconfirmed - Priority - Requester: Important Requested by: Michael Andres (mlandres) Partner organization: openSUSE.org Description: We need to clearly define the way to deal with patterns. - The code11 decision not to install pattern makes them hard to handle. The solver not knowing which patterns were actually selected by the user results in bugs like https://bugzilla.novell.com/show_bug.cgi?id=576059 or https://bugzilla.novell.com/show_bug.cgi?id=676994. It also produces poor results on upgrades, as we can only guess which patterns should be updated. - The approach on opensuse 11.2 to use a package to represent the pattern and it's dependencies might be a step into the right direction (similar to the release-package representing a product). But the link between a pattern and it's prepresenting package is missing. This leads to bugs like https://bugzilla.novell.com/show_bug.cgi?id=592640, where actions like 'set Taboo' on patterns have no effect, because we don't know, thus can't lock, the corresponding package. Another open issue is removal of patterns like in https://bugzilla.novell.com/show_bug.cgi?id=407040. Removing the pattern package with cleanup enabled could be an option. This also requires a link between pattern and package. Whithout a decision accepted by all stakeholders, libzypp/zypper won't be able to resolve several bugs satisfactory. Discussion: #19: Michael Andres (mlandres) (2014-01-27 11:35:53) Done in libzypp-14.7.0 / libsolv-0.4.2 for alpha3. We should be able to drop the old pattern metadata files. -- openSUSE Feature: https://features.opensuse.org/309385