On 08/23/2016 03:25 PM, Simo Sorce wrote:
I have been searching the web to see if we have any hard and fast rule on converting the PEP 440 version names into an RPM NVR that will allow correct upgrades when a Python package is released. In particular in PEP 440 the following ordering is true: 0.2.dev1 < 0.2.a1 < 0.0.b1 < 0.2.rc1 == 0.2.c1 < 0.2 == 0.2.0 < 0.2.post1 I haven't found any Fedora Packaging rules or otherwise any recommendation on transforming a PEP440 package version number to an RPM NVR. The first thing that comes to mind is that the above numbers become r respectively: 0.2.dev1 -> name-0.2.0-0.0.dev1 0.2.a1 -> name-0.2.0-0.1.alpha1 0.2.b1 -> name-0.2.0-0.2.beta1 0.2.rc1 -> name-0.2.0-0.3.rc1 0.2.c1 -> name-0.2.0-0.3.rc1 (yes c -> rc here) 0.2 -> name-0.2.0-1 0.2.0 -> name-0.2.0-1 0.2.post1 -> name-0.2.0-1.post1 if any of the packages need bugfixes they would have to append a release number, ie a patch on post1 would result in name-0.2.0-1.post1.1 Does this make sense ? Should it be written down/agreed/discussed anywhere/somewhere else ?
Isn't this covered by PEP 440 Local Version scheme? https://www.python.org/dev/peps/pep-0440/#id23 -- John -- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/packaging@xxxxxxxxxxxxxxxxxxxxxxx
