rawhide report: 20080211 changes

Ralf Corsepius rc040203 at freenet.de
Sat Feb 16 04:35:21 UTC 2008


On Fri, 2008-02-15 at 16:53 -0600, Jason L Tibbitts III wrote:
> >>>>> "JK" == Jesse Keating <jkeating at redhat.com> writes:
> 
> JK> Erm, I should have restated, you can't conflict with any current
> JK> package in Fedora.
> 
> That would be a new rule, then.

It's a silly rule and renders the purpose of compat-packages widely
non-applicable:

Consider this:

Given a package providing libraries:
libfoo3: /usr/lib/libfoo.so.3

libfoo3-devel: /usr/lib/libfoo.so
libfoo3-devel: /usr/include/foo

Now some other package needs libfoo.so.3's predecessor libfoo.so.2

One way to implement this would be to ship
libfoo2: /usr/lib/libfoo.so2

libfoo2-devel: /usr/lib/libfoo.so
libfoo2-devel: /usr/include/foo


libfoo2-devel would conflict with libfoo3-devel, but the run-time
package libfoo2 would not conflict with libfoo3.

This would allow users wanting to build packages against libfoo2 to
alternatively chose between libfoo3-devel and libfoo2-devel.

Ralf






More information about the fedora-devel-list mailing list