Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Changes between Version 5 and Version 6 of RootLessInstall


Ignore:
Timestamp:
04/29/06 13:22:55 (13 years ago)
Author:
roger.demetrescu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RootLessInstall

    v5 v6  
    33<br> 
    44<div style="display:block; padding: 4px; border: 2px solid red; color: #C00; font-weight:bold;"> 
    5 Note: this entry was moved to TurboGears newsdoc...  
     5Note: this entry was moved to TurboGears newsdoc (RootLessInstall) 
    66</div> 
    77<br> 
    88}}} 
    9  
    10  
    11 I prefer to install turbogears and friends in a user's directory. Here's how I do it: 
    12  
    13 1. ~/.pydistutils.cfg tells distutils where to install things. On OS X mine looks like this: 
    14 {{{ 
    15 [install] 
    16 install_lib = ~/Library/Python/$py_version_short/site-packages 
    17 install_data = ~/Library/Python/$py_version_short/site-packages 
    18 # install_headers = 
    19 install_scripts = ~/bin 
    20 }}} 
    21    This tells distutils to install in my home directory, in a directory the *Framework* build (not system Python) of Python for Mac OS X will look for it. 
    22  
    23    (If I install an extension like numarray it wil include headers, and I may be able to use install_headers to put them in ~/include/ . I have not needed this yet.) 
    24  
    25   For Linux I use this instead, in a layout that mimics the usual /usr/lib/python?.?/site-packages/ or /usr/local/lib/python?.?/site-packages/: 
    26  
    27 {{{ 
    28 [install] 
    29 install_lib = ~/lib/python$py_version_short/site-packages 
    30 install_data = ~/lib/python$py_version_short/site-packages 
    31 install_scripts = ~/bin 
    32 }}} 
    33  
    34 The directive install_data is missing from the PEAK documentation as of 27 Jan. 2005. 
    35  
    36 == With easy_install == 
    37 a  
    38 http://peak.telecommunity.com/DevCenter/EasyInstall#custom-installation-locations explains simple ways to get easy_install to install in a variety of locations. 
    39  
    40 == needs edits == 
    41  
    42 I'd like to see this generalized, because it's a common recipe for any unix-like system. there should also be a note saying that *all* of your easy_installs will follow these rules after these changes.