foo vs. foo+

[Patrice Dumas]

On Sat, Jul 21, 2007 at 04:15:19AM +0200, Christoph Wickert wrote:
> Imagine there are two projects: foo and foo+. foo+ is a fork, a
> different flavor of foo, but both offer the same functionality and are
> compatible for other apps that sit on top of foo(+).
> 
> Now both projects want to be included in fedora. First of all, both
> packages need a Conflicts: foo conflicts foo+ and foo+ conflicts foo.
> 
> Ok so far, but foo+ also needs a "Provides: foo", and I wonder if is 
>   Provides: foo
>   Conflicts: foo
> really is a good idea. And can/should we use versioned Provides: here?

Unless I am wrong, yum (rpm) won't care about versioned Provides:, and 
replace foo+ with foo (I had such issues with libnet10/libnet).

> As foo+ is usually slightly ahead of foo, I'm afraid that yum would
> replace foo with foo+.
> 
> Ideas, Comments?

Maybe use the alternatives system instead of a conflict?

And a virtual provides (maybe versionned) for the foo capability?

--
Pat