tahoe-lafs/setup.py

#! /usr/bin/env python

from distutils.core import setup
from distutils.core import Extension
from distutils.command.build_ext import build_ext
import os, sys


setup(
    name="AllMyData",
    version="0.0.1",
    packages=["allmydata", "allmydata.test", "allmydata.util",
              "allmydata.filetree", "allmydata.scripts",
              ],
    package_dir={ "allmydata": "src/allmydata",
                  },
    scripts = ["bin/allmydata-tahoe"],
    package_data={ 'allmydata': ['web/*.xhtml'] },

    description="AllMyData (tahoe2)",
    )
change #!/usr/bin/python to #!/usr/bin/env python Note that using "whatever version of python the name 'python' maps to in the current shell environment" is more error-prone that specifying which python you mean, such as by executing "/usr/bin/python setup.py" instead of executing "./setup.py". When you build tahoe (by running "make") it will make a copy of bin/allmydata-tahoe in instdir/bin/allmydata-tahoe with the shebang line rewritten to execute the specific version of python that was used when building instead of to execute "/usr/bin/env python". However, it seems better that the default for lazy people be "whatever 'python' means currently" instead of "whatever 'python' meant to the manufacturer of your operating system". 2007-03-29 14:01:28 -07:00			`#! /usr/bin/env python`
add distutils-based packaging 2006-12-05 01:29:26 -07:00
			`from distutils.core import setup`
first cut at creating allmydata.Crypto, starting with python-amycrypto-2.0.1.allmydata2 (with working CTR mode) 2006-12-14 03:25:30 -07:00			`from distutils.core import Extension`
			`from distutils.command.build_ext import build_ext`
			`import os, sys`
add distutils-based packaging 2006-12-05 01:29:26 -07:00
first cut at creating allmydata.Crypto, starting with python-amycrypto-2.0.1.allmydata2 (with working CTR mode) 2006-12-14 03:25:30 -07:00
add distutils-based packaging 2006-12-05 01:29:26 -07:00			`setup(`
			`name="AllMyData",`
			`version="0.0.1",`
move all packages into src/, fix allmydata.Crypto build. Now you must perform a 'setup.py build' before using anything, and you must add the build directory (build/lib.linux-i686-2.4) to your PYTHONPATH before doing anything 2006-12-14 03:39:50 -07:00			`packages=["allmydata", "allmydata.test", "allmydata.util",`
split filetree_new.py up into smaller pieces, in a new subpackage 2007-01-17 13:54:38 -07:00			`"allmydata.filetree", "allmydata.scripts",`
first cut at creating allmydata.Crypto, starting with python-amycrypto-2.0.1.allmydata2 (with working CTR mode) 2006-12-14 03:25:30 -07:00			`],`
move all packages into src/, fix allmydata.Crypto build. Now you must perform a 'setup.py build' before using anything, and you must add the build directory (build/lib.linux-i686-2.4) to your PYTHONPATH before doing anything 2006-12-14 03:39:50 -07:00			`package_dir={ "allmydata": "src/allmydata",`
add __init__ and setup.py glue for py_ecc, so we can import it 2007-01-01 23:43:24 -07:00			`},`
rename bin/allmydata to bin/allmydata-tahoe, so the package can co-exist with the regular (amdlib) package 2007-01-19 20:05:33 -07:00			`scripts = ["bin/allmydata-tahoe"],`
add distutils-based packaging 2006-12-05 01:29:26 -07:00			`package_data={ 'allmydata': ['web/*.xhtml'] },`
first cut at creating allmydata.Crypto, starting with python-amycrypto-2.0.1.allmydata2 (with working CTR mode) 2006-12-14 03:25:30 -07:00
add distutils-based packaging 2006-12-05 01:29:26 -07:00			`description="AllMyData (tahoe2)",`
			`)`