pidgin obsoleting itself

Michael Schwendt mschwendt at gmail.com
Wed Jun 9 10:49:08 UTC 2010


On Wed, 09 Jun 2010 11:23:49 +0100, Paul wrote:

> The Obsoletes: in pidgin-evo causes pidgin-evo to be pulled in, which is 
> fine. The package should obsolete pidgin packages prior to the split but 
> not the ones after the split.

Sounds [more] correct.

> > * We need to not erase main pidgin (Obsoletes in pidgin)
> 
> Not needed if pidgin-evo depends on pidgin itself - the regular 
> dependency mechanism should pull the main pidgin package in. And since 
> the new pidgin package is versioned later than the split, it's no longer 
> obsoleted by the pidgin-evo subpackage. Does that not work?

That is closer to ordinary package renaming,

  A renamed to B  :  B obsoletes A + B provides A

with the exception that B does not provide A, but requires a specific
version of A.

  A => pidgin
  B => pidgin-evolution


More information about the devel mailing list