Bug 149843

Summary: Python's site-packages should contain a directory in /usr/local.
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Karl Pietrzak <kap4020>
Component: OtherAssignee: Jan Matejek <jmatejek>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Karl Pietrzak 2006-02-10 01:57:44 UTC
1. There should be a site-packages directory   
in /usr/local,   
probably /usr/local/lib/python/site-packages.  Just   
like in /usr, it'll need the appropriate symlinks.    
x86_64 bit issues also need to be taken into account,   
so /usr/local/lib64/python2.4/site-packages should be   
the local site-packages directory for Python 2.4.x on   
a x86_64 machine.   
   
The reasons for these are numerous.  $PATH   
contains /usr/local/bin, $GTK_PATH   
contains /usr/local, $MANPATH   
contains /usr/local/share/man, and $PKG_CONFIG_PATH   
contains /usr/local/lib/pkgconfig.  Adding a   
site-packages directory in /usr/local will simply   
fill in the hole in the Python configuration.   
   
As the FHS points out, /usr may very well be mounted   
read-only for security purposes.  /usr/local should   
be used instead, especially for non-system / testing   
software.   
   
2. Distutils should install, by default, in   
the site-packages directory in /usr/local described  
in part (1).  This will simply mimic the auto(conf| 
make|etc.) default installation path (isn't the  
default installation path for Python  
itself /usr/local?).  
  
For simplicity and consistency's sake, the default  
installation path for distutils should be the 
site-packages directory in /usr/local.
Comment 1 Jan Matejek 2006-02-17 12:47:04 UTC

*** This bug has been marked as a duplicate of 149809 ***