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 2 and Version 3 of DebianInstall


Ignore:
Timestamp:
12/27/05 10:38:36 (13 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DebianInstall

    v2 v3  
    11== Debian Packaging == 
     2 
     3Unlike other Linux distributions, Debian systems use a strict package management system. This system "owns" certain directories. If a user installs files into the directories, he is likely to corrupt the system. Unfortunately, the current TurboGears install instructions for *nix systems will override filesystem permissions, deposit files ino those directories, and corrupt your Debian system (possibly quite badly!). This is listed as bug 273. 
     4 
     5Instead of those directions, there are two solutions for installing TurboGears. You can do it through the Debian package system, by trying to create a Debian package representing the python module (method 1). Or you can set up configurations so that the python packaging system will respect the boundaries required by Debian packaging system (method 2). 
     6 
     7The second method is recommended. The easy-deb below is not included in Debian stable, seems fairly new, and it will probably be a while before a best practice emerges for integrating the python packaging system with Debian's package management.  
     8 
     9== 1) Through the Debian package system == 
    210 
    311Ian Bicking noted that there is a python tool for creating Debian packages: 
    412http://easy-deb.sourceforge.net/ 
    513 
    6 == Debian Sarge and Sid (unstable): Non-root installs == 
     14== 2) Debian Sarge and Sid (unstable): Non-root installs == 
    715 
    816Here $ is your prompt. 
     
    5260$ python2.4 ez_setup.py -f http://www.turbogears.org/download/index.html --script-dir /usr/local/bin TurboGears 
    5361}}} 
     62 
     63A known-good variant of these instructions is also available at bug ticket 273.