Hi On Thu, Feb 28, 2013 at 11:22 AM, Matthias Runge wrote:
> I see your point not to touch any Django-package to change the > requirements, but also this will make things more confusing: > Django (as F17) is 1.4.x > python-django is 1.4.x > python-django15 is 1.5 > > what about Django-1.6? So I'd prefer to have python-django as moving > target and fix the release by appending the version. > Well, if the current python-django in Fedora is renamed to python-django14 and appropriate provides are added to the EPEL version such that django dependent packages don't have to bother with if else in spec files, you wouldn't need any moving targets at all. The version number will be right there in the package name and it will be obvious which version it is. If Django stops breaking compatibility, we can revisit this. Rahul
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
