On Fri, Mar 1, 2013 at 2:47 PM, Stephen Gallagher <sgall...@redhat.com> wrote:
> Well, I'm also looking at EPEL here (though I suppose we could just
> implement a different solution on that side as well). EPEL has a much
> longer life than Fedora releases (and much, much longer than the
> Django upstream release maintenance period). So we need to have a plan
> in place for how to keep EPEL moving forward sanely. In my humble
> opinion, we should break things *once* so that packages learn to make
> a dependency on a specific Django version (by doing a Requires:
> python-django14) and drop the historical "Django" and unversioned
> "python-django" Provides from any of the packages.
Note that the provides/requires are not necessarily tied to package
names. There is sufficient prior art - quite a few languages have
special ABI/API "marker" provides/requires while still having an
unversioned package name.
Mirek
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
