On Wednesday, 06 May 2009, at 18:05:23 (-0400),
Jeff Johnson wrote:

> So how do I solve this problem? For better or worse, packages do get
> renamed, and its common packaging practice to add an Obsoletes: when
> doing so. It just doesn't work like expected.

Seems to me that the logical course of action, should permanence be
desired, would be to add Conflicts: old-name <= %{version}-%{release}

That way the other package can't be installed while the new one is.

> (other quite cogent arguments snipped but not ignored)

:-)

Michael

-- 
Michael Jennings (a.k.a. KainX)  http://www.kainx.org/  <mej@kainx.org>
Linux Server/Cluster Admin, LBL.gov       Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
 "The notion that something as complex and thermodynamically
 improbable as life could form out of a bit of ooze is about as
 believable as a jet airliner being assembled during a hurricane in a
 junkyard."                       -- Fred Hoyle (quoted by Sonia Shah)