[oclug] rpm and obsoleted packages

[Michael P. Soulier]

On 16/06/03 Gilles J. Seguin did speaketh:

> I am questionning, why are you using this features.
> Because I do not want to see it used.
> <http://www.redhat.com/advice/speaks_backport.html>
> 
> That is, a rpm package that removed one or many other packages

    I see nothing in on the page you reference that pertains to this
discussion. 
    I'm using the obsoletes feature for what it was intended. In many
cases we've renamed packages, or obsoleted them because their
functionality is provided elsewhere, it obsoletion is necessary to avoid
a file conflict. 

> The tag conflict is suppose to do that.
> That is, stop installing a package because of the presence of
> some files or VERSION number.

    Depending on why the package was obsoleted, the new package can very
well prevent you from installing the old package, unless you force it.
Take the file conflict example. 

    If both packages own /foo/bar/bash, you can't install them both
without overriding rpm's default behaviour.

    As far as I can tell, the Conflicts tag works identically to the
Obsoletes tag. 

    Mike

-- 
Michael P. Soulier <msoulier at digitaltorque.ca>, GnuPG pub key: 5BC8BE08
"...the word HACK is used as a verb to indicate a massive amount
of nerd-like effort."  -Harley Hahn, A Student's Guide to Unix
HTML Email Considered Harmful: http://expita.com/nomime.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://tux.oclug.on.ca/pipermail/oclug/attachments/20030616/cbb8d744/attachment.bin