it depends :-)
RPM's great weakness is that everything depends on the naming convention chosen by the RPM author. It is the _RedHat_ Package Manager after all, and when they wrote it I don't think it occurred that other distro companies would exist, much less adopt the package format (IIRC Slackware was the only other distro when RH got started, though TurboLinux came up very quickly too).
When packages are selected, the urpmi mechanism looks at [name][version]. When [name] matches, [version] is compared and the requires rules are applied.
If [name] doesn't match, you end up with a problem because the two packages are considered different by the RPM database, but they contain the same files. You get an error "foo-bar.3.0.i586.mdk.rpm is trying to overwrite /bin/foobar which is owned by foobar.2.9.i586.mdk.rpm".
If [version] doesn't sort the way you expect, you might end up with packages not getting updated. Example left to imagination.
If urpmi just can't figure it out, it'll ask: "You need to choose one of the following packages: 1) libfoobar3-devel-0.i586.mdk.rpm 2) libfoobar-devel.3.0.i586.mdk.rpm Please enter your choice or cancel: "
Jack
On Sun, 2003-06-08 at 08:42, Trey Sizemore wrote:
If I have Cooker and Texstar both installed, how will running:
urpmi --auto --auto-select
handle duplicate packages (for example, Texstar's kdebase and the Cooker kdebase)?
Thanks.
Beware that urpmi will automatically choose the most recent version of your installed package(s) to install, i.e., cooker. For that reason, you probably should not have a cooker source configured unless you are running cooker. Alternatively, you can specify which media to use when running urpmi, e.g.:
urpmi --media texstar --auto-select
Rolf
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
