> On Oct 29, 2014, at 2:36 PM, Marcus Smith <qwc...@gmail.com> wrote: > > > This is the kind of direction we're also exploring for Fedora & EPEL: setting > up a distro specific devpi instance so we can automatically publish distro > compatible wheel files, as well as separating the distro level licencing and > preliminary security review step from the step of repackaging in a language > independent format. (I need to set up a curated PyPI mirror for work anyway, > and since I work at Red Hat, and the Fedora community are open to the idea, > we're working on it upstream rather than inside the firewall) > > > Btw, I've been doing this at my company, that is maintaining separate wheel > indexes per platform we need (in our case, cent5 and cent6). > One problem here is that it's possible for pip download caches to get > "corrupted" with the wrong distributions (i.e. the incompatible ones), since > the distributions are not distinguishable by name > Would Fedora really consider releasing a public service where there fedora > release is not represented in the distribution name? or would you be wanting > to get more tagging spec'd out in Wheel 2.0 first? > > P.S. In looking at the PEP425/427 specs again, I'm slightly confused about > the "build tag". It's barely covered, but I can imagine using that possibly > to distinguish dists, assuming pip support was added, alhough it's supposed > to start with a number, which doesn't seem to fit the use case we'd want. > > > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig
It’s a build number, it’s used incase you need to rebuild a Wheel using the same source files. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
