[Python-Dev] FHS compliance of Python installation (original) (raw)
James Y Knight foom at fuhm.net
Sat Jun 26 23:10:42 CEST 2010
- Previous message: [Python-Dev] FHS compliance of Python installation
- Next message: [Python-Dev] versioned .so files for Python 3.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Jun 26, 2010, at 4:35 PM, Matthias Klose wrote:
On 26.06.2010 22:30, C. Titus Brown wrote:
On Sat, Jun 26, 2010 at 10:25:28PM +0200, Matthias Klose wrote:
On 25.06.2010 02:54, Ben Finney wrote:
James Y Knight<foom at fuhm.net> writes:
Really, python should store the .py files in /usr/share/python/, the .so files in /usr/lib/x8664- linux-gnu/python2.5-debug/, and the .pyc files in /var/lib/python2.5- debug. But python doesn't work like that. +1 So who's going to draft the ???Filesystem Hierarchy Standard compliance??? PEP? :-) This has nothing to do with the FHS. The FHS talks about data, not code. Really? It has some guidelines here for object files, etc., at least as of 2004. http://www.pathname.com/fhs/pub/fhs-2.3.html A quick scan suggests /usr/lib is the right place to look: http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA agreed for object files, but http://www.pathname.com/fhs/pub/fhs-2.3.html#USRSHAREARCHITECTUREINDEPENDENTDATA explicitely states "The /usr/share hierarchy is for all read-only architecture independent data files".
I always figured the "read-only architecture independent" bit was the
important part there, and "code is data". Emacs's el files go into /
usr/share/emacs, for instance.
James
- Previous message: [Python-Dev] FHS compliance of Python installation
- Next message: [Python-Dev] versioned .so files for Python 3.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]