[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Upgrading an RPM with a different name



On Mon, Aug 23, 2004 at 01:53:01PM -0600, Bart Whiteley wrote:
> On Monday 23 August 2004 01:48 pm, Yochai Shefi-Simchon wrote:
> > Hi,
> > 
> > I'd like to create an RPM called newname. When installed on a computer
> > which has the RPM called oldname already installed, I'd like the
> > newname RPM to completely replace the oldname RPM. That is, newname is
> > actually an upgrade to oldname.
> > 
> > Is there a way to do that? Or is the only way to put a "Conflicts:
> > oldname" tag in the newname RPM and expect the user to manually remove
> > oldname before installing newname?
> > 
> 
> In newname.spec, you should include: 
>   Obsoletes: oldname
>   Provides: oldname
>   Conflicts: oldname
> 
> Now newname will be an upgrade to oldname, and will even provide "oldname" in
> case some other package depends on "oldname" (but "newname" also satisfies 
> the requirement). 
> 

All of the above should express the last known version of oldname
deployed. Assuming that epoch/version/release is E:V-R, then

   Obsoletes: oldname <= E:V-R
   Provides: oldname = E:V-R
   Conflicts: oldname <= E:V-R

starts to do the right thing.

73 de Jeff

-- 
Jeff Johnson	ARS N3NPQ
jbj@redhat.com (jbj@jbj.org)
Chapel Hill, NC



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]