http://bugzilla.novell.com/show_bug.cgi?id=592640 http://bugzilla.novell.com/show_bug.cgi?id=592640#c8 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mc@novell.com AssignedTo|zypp-maintainers@forge.prov |coolo@novell.com |o.novell.com | --- Comment #8 from Michael Andres <ma@novell.com> 2010-04-01 13:36:02 UTC --- The curse of code11 pattern handling. I pass it to Coolo, as he broke it by introducing the patterns-openSUSE-* packages. By duplicating all dependencies on the package layer, one is still able to trigger installation of AA by selecting the pattern, but locking the pattern has no effect, as it does not affect the package layer. UI: pattern:base --recommends--> pattern:AppArmor | | requires requires v v Packages: patterns-openSUSE-base --recommends--> patterns-openSUSE-apparmor If we want a solution for 11.3 (and also future SLE) we should think about it ASAP. We could think about dropping patterns (also product) as primary solvable objects in the pool. Instead represent them as specialized packages. But that will also have some impact on zypper, pkgkit and the UIs. A probably cheaper solution is the same approach as we currently have for products. We let the pattern and the representing package share the same status (selecting the pattern in fact selects the packages). All dependencies must be expressed on the package level. As the objects would stay in the pool, there should be almost no impact on zypper, pkgkit and the UIs (but mls@ will sigh). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.