On 4 December 2013 23:25, Daniel Holth <dho...@gmail.com> wrote:
> On Wed, Dec 4, 2013 at 6:10 AM, Nick Coghlan <ncogh...@gmail.com> wrote:
>> == Regarding custom installation directories ==
>>
>> This technically came up in the cobblerd thread (regarding installing
>> scripts to /usr/sbin instead of /usr/bin), but I believe it may also
>> be relevant to the problem of shipping external libraries inside
>> wheels, static data files for applications, etc.
>>
>> It's a little underspecified in PEP 427, but the way the wheel format
>> currently handles installation to paths other than purelib and platlib
>> (or to install to both of those as part of the same wheel) is to use
>> the sysconfig scheme names as subdirectories within the wheel's .data
>> directory. This approach is great for making it easy to build
>> well-behaved cross platform wheels that play nice with virtual
>> environments, but allowing a "just put it here" escape clause could
>> potentially be a useful approach for platform specific wheels
>> (especially on *nix systems that use the Filesystem Hierarchy
>> Standard).
>>
>> I've posted this idea to the metadata format issue tracker:
>> https://bitbucket.org/pypa/pypi-metadata-formats/issue/13/add-a-new-subdirectory-to-allow-wheels-to
>
> Note the 'data' sysconfig directory is already just '/' or the root of
> the virtualenv.

Ah, nice - I didn't grasp that from the sysconfig docs, and it's
definitely not covered in PEP 427 (it currently glosses over the
install scheme directories without even a reference to sysconfig)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Reply via email to