On 28 December 2013 16:00, Nick Coghlan <[email protected]> wrote: > On 28 December 2013 06:02, Chris Barker <[email protected]> wrote: >> Then the python distro would map these to actual paths at install time: gnu >> systems would map the gnu locations, Windows to Windows-appropriate >> locations, OS-X to OS-X locations, etc.... This wold also allow python >> distros like Anaconda or macports python, or ??? to do their own thing, >> which may not be putting everything in /usr/local, or ... >> >> That may be what you had in mind, but I got confused. > > There's no concrete proposal on the table at this point in time - just > an acknowledgement that this is a use case the wheel format doesn't > yet handle (sdists can handle it due to the way that setuptools > handles the data_files option). > > However, any concrete proposal will likely use the GNU structure as > the basis for "kinds of files" rather than inventing a new > Python-specific naming scheme (or make an extremely compelling case > for inventing our own custom scheme), and on Windows and Mac OS X, > many of those will likely just map to dumping things in the app > directory (or the application data directory in the case of Windows).
The other main thing to look at in terms of current state of the art is npm, for both structure and hooks. https://npmjs.org/doc/files/npm-folders.html https://npmjs.org/doc/files/package.json.html https://npmjs.org/doc/misc/npm-scripts.html npm is basically a full-blown platform packaging system (covering config, runtime scripts, etc), but with a heavily POSIX biased bent (even moreso than the Python ecosystem). Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
