Re: Upgrading an RPM with a different name

[James Olin Oden <joden lee k12 nc us>]

On Mon, 23 Aug 2004, 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). 
> 
> 
That's cool (the Provides).   But why do the Conflicts also?

Cheers...james