On 20 July 2015 at 11:42, Leonardo Rochael Almeida <leoroch...@gmail.com> wrote: > To solve this problem, so far we've only been able to come up with two > extremes: > > - Have the libraries contain enough metadata in their source form that we > can generate true system packages from them (this doesn't really help the > virtualenv case) > - Carry all the dependencies. Either by static linking, or by including all > dynamic libraries in the wheel, or by becoming something like Conda where we > package even non Python projects.
We keep stalling on making progress with Linux wheel files as our discussions spiral out into all the reasons why solving the general case of binary distribution is so hard. However, Nate has a specific concrete problem in needing to get artifacts from Galaxy's build servers and installing them into their analysis environments - let's help him solve that, on the assumption that some *other* mechanism will be used to manage the non-Python components. This approach is actually applicable to many server based environments, as a configuration management tool like Puppet, Chef, Salt or Ansible will be used to deal with the non-Python aspects. This approach is even applicable to some "centrally managed data analysis workstation" cases. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
