Commit Graph

9 Commits

Author SHA1 Message Date
Brian Warner
f5a7eb0ad5 bin/tahoe: rename 'allmydata-tahoe' in some comments 2007-10-11 03:39:29 -07:00
Brian Warner
dc573554c8 rename bin/allmydata-tahoe to bin/tahoe. Closes . 2007-10-11 03:38:24 -07:00
Brian Warner
b3b94d24df bin/allmydata-tahoe: fix handling of PYTHONPATH, we were missing an os.pathsep
which would cause a pre-existing PYTHONPATH to get mangled
2007-09-17 03:43:22 -07:00
Brian Warner
3a8da0c1cc bin/allmydata-tahoe: update to new src/ + support/ directories, remove instdir/bin check 2007-09-14 19:24:28 -07:00
Brian Warner
e5fdf0daca bin/allmydata-tahoe: also update PYTHONPATH so that child processes (like twistd) will work 2007-06-06 11:36:48 -07:00
Brian Warner
3c0485204e bin/allmydata-tahoe: add a sys.path-modifying preamble to make it easy to run from source 2007-06-06 11:24:00 -07:00
Zooko O'Whielacronx
4b4f5bbcba 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
Brian Warner
26b01a9808 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
Brian Warner
aec1d1eecc add bin/allmydata to create/stop/start nodes 2006-12-05 12:25:23 -07:00