http://bugzilla.novell.com/show_bug.cgi?id=498556 User ma@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=498556#c7 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |ma@novell.com Resolution| |INVALID --- Comment #7 from Michael Andres <ma@novell.com> 2009-09-01 06:30:56 MDT --- - A package is something you can actually install. - This is not true for a patch. A patch is just a bunch of constraints! I try to explain: A patch can assert that in case you are using a package 'Foo', your system contains at least version 2, because e.g. version 1 is buggy. To do so, the patch contains a dependency conflicting with "Foo < 2". The dependency is broken if the system contained "Foo-1", and it is fulfilled if the system contains "Foo-2", or no Foo is installed. If a patchs dependency is broken, the patch is considered being as 'NEEDED' (Foo-1 installed). If the dependencies are fine, the patch is called 'SATISFIED' (Foo-2 installed). This is basically how patches are classified. (Patches which are satisfied, because the do not mention a single installed package, are called "IRRELEVANT'(no Foo installed).) Selecting a patch, simply activates the dependencies for the next solver run. The solver will now try to satisfy all constraints. It will suggest to install "Foo-2", if "Foo-1" is installed and the (needed) Foo-patch was selected. But if the Foo-patch is already satisfied (Foo-2 installed), its constraints are fulfilled and so they will not cause any additional action. This is why selecting satisfied and irrelevant patches will never cause a package to be installed. -- 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.