patches (was Re: linux security)

[Jesse Keating]

On Thu, 23 Jan 2003 08:43:32 -0800 (PST)
Jeff Silverman <jeffs at duet.cfr.washington.edu> wrote:

> 
> For a long time, I have either installed or upgraded software on RPMs 
> using the 
> 
> rpm -Uvh PACKAGE-new_version
> 
> command.  If I understand what you are telling me, I should use the 
> 
> rpm -ivh PACKAGE-new_version
> 
> command, and then when I am ready to get rid of the old version, use
> 
> rpm -evh PACKAGE-old_version
> 
> to get rid of the old version? 

It depends on the package.  Some library packages, like openssl, have
different versions:  openssl-0.9.6b-29.i386.rpm, and
openssl096-0.9.6-11.i386.rpm, and openssl095a-0.9.5a-16.i386.rpm.  I do
believe that all 3 of them can co-exist in the same vendor space.  The
key to this is the way the package is named.  openssl096 is all crammed
together, which makes it a completely different package from
openssl-foo.  You'll find this w/ automake and some of the other dev
tools.

> But, if I am installing a patch or a minor update to an existing
> package, then go ahead and use
> 
> rpm -Uvh PACKAGE-new_version
> 
> I guess I am asking for a more detailed policy of when to use -i and
> when to use -U

There isn't really a clear guide to this... if the package allows it
(usually you'll be able to tell by the naming of the package) and you
find yourself needing both versions, install them both w/ ivh.  Of
course, since the package names are different, you can't use -Uvh (as
you would normally expect), since it won't remove the "older" package.

-- 
Jesse Keating RHCE MCSE
For Web Services and Linux Consulting, Visit --> j2Solutions.net
Mondo DevTeam (www.mondorescue.org)

Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=jkeating