> On Jun 22, 2016, at 12:21, Nathaniel Smith <n...@pobox.com> wrote: > There are still use cases for distro-specific wheels, though -- some examples > include Raspbian wheels (manylinux1 is x86/x86-64 only), Alpine Linux wheels > (manylinux1 is glibc only), internal deploys that want to build on Ubuntu > 14.04 and deploy on 14.04 and don't need the hassle of generating > manylinux-style binaries but would like a more meaningful platform tag than > "linux", and for everyone who wants to extend wheel metadata to allow > dependencies on external distro packages then having distro-specific wheels > is probably a necessary first step. >
If we want to treat distros as first-class deployment targets I think being able to use their platform features in a way that's compatible with PyPI is an important next step. However, wheel tags might be insufficient here; the main appeal of creating distro-specific wheels is being able to use distro-specific features, but those typically come along with specific package dependencies as well, and we don't have a way to express those yet. I think this is worthwhile to do, but figuring out a way to do it is probably going to take a lot of discussion. -glyph
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
