On Wed, Apr 10, 2013 at 07:53:28AM -0400, Stephen Gallagher wrote: > > Actually, I just realized that this is NOT going to provide a clean > upgrade path. If you change the Requires: to python-django14, it means > that when upgrading an app, yum is going to attempt to install > python-django14 on systems that already have python-django, which will > result in an implicit conflict. > > There are two things that should probably be done to solve this: > 1) All applications should change Requires: python-django to > Requires: python-django >= 1.4 > Conflicts: python-django >= 1.5 > > Since the python-django14 package Provides: python-django = 1.4.5, > this will cleanly move upgrades along to the python-django14 package > if needed. > > > 2) The python-django14 package should add: > Obsoletes: python-django < 1.5 > Conflicts: python-django >= 1.5 > > This way, anyone who is currently running python-django = 1.4.x will > continue along the 1.4.x upgrade path until they explicitly switch to > 1.5. Also, since the packages are not mutually-compatible, they really > need to have the explicit Conflicts. > > It should be safe to use Obsoletes < $current_version because we will > only ever be supporting in Fedora the two versions supported by > upstream. It gets a little hazy with EPEL, but given that upstream has > abandoned the older releases, they should probably get retired eventually. > > Adding Toshio to the CC list explicitly to check my logic :) Conflicts will run afoul of the guidelines. I thought these were parallel installable? -Toshio
Attachment:
pgpLH3Y3CqZ39.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
