Le Vendredi 01 Ao�t 2003 17:39, Fran�ois Pons a �crit : > > 1. rpmbuild -ba dummy1, dummy2-1mdk, and dummy2-2mdk. > > 2. rpm -Uvh dummy1-1.0-1mdk.noarch.rpm > > now dummy1 is installed > > 3. rpm -Uvh dummy2-1.0-1mdk.noarch.rpm > > now dummy1 and dummy2 are both installed > > 4. rpm -Uvh dummy2-1.0-2mdk.noarch.rpm > > now dummy1 is gone; onldummy2 is installed > > Simpler case, do step 1, 2, 4 without 3. > > Version of obsoletes are not used, but version of packages are used > directly, this is the behaviour of the fixes taken from rpm-4.2.1.
Let me understand... If rpm don't use the version put on the obsoletes, but directly the package version, why we still can put a version to an obsolete ? If it do this only if obsoletes version is missing, how to be sure we obsoletes all version for a rpm ? The management can change, but it is illogical to me eyes. Worst, how can obsoletes a soft only for a version, like some kde packages can need. Can you explain quickly what are "color tag" ? I know only colour setup by vim when I edit a spec file. -- Linux pour Mac !? Enfin le moyen de transformer une pomme en v�ritable ordinateur. - JL. Olivier Thauvin - http://nanardon.homelinux.org/
