On Tue, Aug 23, 2016 at 4:11 PM, Neal Gompa <ngompa13@xxxxxxxxx> wrote: > On Tue, Aug 23, 2016 at 3:25 PM, Simo Sorce <simo@xxxxxxxxxx> 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 >> > > If we were allowed to, I'd probably structure like so in the Version field: > > 0.2~0.dev1 < 0.2~a1 < 0.2~b1 < (0.2~rc1 | 0.2~c1) < ( 0.2 | 0.2.0 ) < 0.2+post1 > > To me, this is more natural than doing the weird release hacking we do now. > I'd also like to note that this also rather cleanly handles structures like the following: 0.2.dev1+post2 => 0.2~0.dev1+post2 This scheme is possible in all Fedora versions and at least in EL6 and up. -- 真実はいつも一つ！/ Always, there's only one truth! -- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/packaging@xxxxxxxxxxxxxxxxxxxxxxx
