[Wheel-builders] libpythonX.Y.so.1

[Robert T. McGibbon]

> What do you have in mind?

I'm not 100% sure.

One thing is that I was thinking that the information could be returned
from `auditwheel show` kind of like a "report card". To be more concrete,
the manylinux1 policy has a couple different prongs, like symbol versions,
external libraries, etc. So it could be presented as an easy to understand
table or something: "Your wheel passes on X, but needs work on Y", or
something. I was also thinking about using ASCII colors in the output to
make this easier to visually parse.

Another thing is that currently, `auditwheel repair` just vendors all
shared libraries into the wheel. I think Nathaniel mentioned that it might
be a good idea to be a little more discerning -- maybe require the user to
list libraries individually or something. Obviously there's often a
licensing concern with vendoring in external shared libraries that might be
GPL, so we probably want to somehow, through the UX, make sure that the
user is aware of the consequences of their choices and isn't put in a
situation where they might accidentally violate the GPL without their
knowledge or intent.

-Robert




On Thu, Mar 3, 2016 at 8:36 AM, Nate Coraor <nate at bx.psu.edu> wrote:

> On Wed, Mar 2, 2016 at 12:57 PM, Robert T. McGibbon <rmcgibbo at gmail.com>
> wrote:
>
>> Hey guys,
>>
>> Sorry I'm out of the loop. Nathaniel correctly diagnosed the problem as
>> thesis stuff. Quick responses below:
>>
>> > 1. With SOABI tag support now available for Python 2.X, would a PR
>> adding UCS-2 builds of Python to the docker image be accepted?
>>
>> +1 from me. I think there's an issue open for this. You just need to
>> decide something rational for the directory layout of which Python goes
>> where and what the symlinks will be.
>>
>> I think this will also require getting the UCS-2 detection code properly
>> removed from auditwheel (https://github.com/pypa/auditwheel/pull/17).
>> Sorry I haven't done that yet.
>>
>
> Okay, I'll get going on these.
>
>
>> > 2. Is anyone working on the pip side of the changes necessary to
>> install manylinux1 wheels? If not, I'll do this.
>>
>> IIRC, there is an open PR to pip (https://github.com/pypa/pip/pull/3497).
>> I think adding your voice there might help move it along. I think that PR
>> is ready to merge, but just lacking the last necessary push from a pip
>> maintainer to merge it.
>>
>>
>> > Also, I wonder if we should vendor auditwheel into wheel itself so you
>> can directly build manylinux1 wheels.
>>
>> IMO it's too early for that. auditwheel is not mature, and besides you
>> really need the docker env. On that note, any help getting auditwheel in
>> better shape -- especially UX-wise if you have any free cycles -- would be
>> totally awesome.
>>
>
> What do you have in mind?
>
> --nate
>



-- 
-Robert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/wheel-builders/attachments/20160303/60e583c1/attachment.html>