dc573554c8
rename bin/allmydata-tahoe to bin/tahoe. Closes #155 .
2007-10-11 03:38:24 -07:00
84a303515f
setup: use ez_setup.py without a "download delay"
2007-10-03 15:14:14 -07:00
a9bb0814e6
setup.py use sys.executable instead of hard-coded 'python' to run make-version.py
2007-09-24 12:38:59 -07:00
2ff4f30e64
setup: attempt to invoke make-version.py whenever setup.py is evaluated
2007-09-23 18:43:36 -07:00
6fbc51568f
setup: use the setuptools "console_scripts" feature to get an allmydata-tahoe.exe on Windows
2007-09-21 13:56:27 -07:00
1f035a8f1f
setup.py: factor out dependency stuff, add workaround for nevow-0.6.0-on-dapper problem
2007-09-15 15:05:35 -07:00
5cc1dbaac9
setup.py: add Nevow to our dependency list
2007-09-15 14:18:07 -07:00
fb5ec5a899
setup.py: minor reformatting, use explicit file: URLs in dependency-links
2007-09-15 14:05:32 -07:00
44c7349270
setup.py: require simplejson>=1.4, since we use the indent= argument
2007-09-14 03:24:15 -07:00
9c272308e2
set the zip_safe flag to False
...
This means that by default the allmydata-tahoe egg will be a directory with a tree of files instead of a zip file containing files. I prefer the former because it makes it easier for people to hack into it.
Unfortunately the files therein are still going to be .pyc's instead of .py's, if I understand correctly. I would prefer for them to be .py's. See also discussion on the distutils-sig mailing list:
http://mail.python.org/pipermail/distutils-sig/2007-July/007827.html
2007-09-13 15:37:55 -07:00
ef7340fb77
change setup.py to find dependency tarballs in misc/dependencies
2007-09-13 15:37:27 -07:00
28ac048ba0
change ez_setup.py to find tarballs in misc/dependencies
2007-09-13 14:51:19 -07:00
a01ccc54c0
use ez_setup.py to bootstrap setuptools
2007-09-12 18:57:10 -07:00
7853497787
setup.py: remove nevow dependency: we need it, but easy_install can't install it
2007-09-12 16:55:38 -07:00
1c27cc3ea8
packaging: move to setuptools
2007-09-12 16:02:53 -07:00
93554c8072
setup.py: fix move to _version.py
2007-09-12 16:02:23 -07:00
f4b5fbc418
README: update the wording of the "LICENCE" section to more closely follow FSF recommendations
2007-09-12 11:31:57 -07:00
0fe1205789
storage: replace sqlite with in-share lease records
2007-09-02 14:47:15 -07:00
2a63fe8b01
deletion phase3: add a sqlite database to track renew/cancel-lease secrets, implement renew/cancel_lease (but nobody calls them yet). Also, move the shares from BASEDIR/storage/* down to BASEDIR/storage/shares/*
2007-08-27 23:41:40 -07:00
56e7ecc540
setup.py: oops, I inserted a typo by commenting out the wrong line
2007-08-16 00:56:58 -07:00
ec1fa9cd5d
setup.py: don't install allmydata.Crypto.PublicKey either
2007-08-16 00:54:52 -07:00
9146924271
setup.py: disable building RSA for now, since it requires GMP. We'll refrain
...
from adding it to the build-dependencies until we actually want to use RSA.
2007-08-16 00:52:21 -07:00
6c24848797
copy RSA from PyCrypto into the allmydata/ tree, we'll use it eventually
2007-08-15 17:36:39 -07:00
b7703df6a5
remove PyCrypto, copy AES/SHA256/Util.number into the allmydata/ tree
2007-08-14 13:57:41 -07:00
4de5767c98
web: remove /vdrive/private, replace with a start.html file that points at the /uri/PRIVATE_URI, to prevent XSRF attacks
2007-08-22 14:54:34 -07:00
4a0682874b
remove old filetree code
2007-06-25 20:34:19 -07:00
1eba30cd14
webish.py: put the URI in a narrower auto-scrolling box (with CSS)
2007-06-15 01:32:20 -07:00
3d1adf6d30
update docs, remove extraneous licence text, sort module names in import statement
...
closes #46 ?
2007-05-21 13:42:51 -07:00
3f6b660272
update version-number handling, pull release tags from darcs history
2007-05-03 20:14:07 -07:00
d41e944beb
re-re-factored the download and install instructions
...
Now the instructions about how to download debian packages live on a separate
page of the wiki instead of on the front page or in the README. The README is
only about building from source. The front page contains pointers to those two
other pages (the debiandownloadpage and the README).
2007-05-02 12:54:26 -07:00
40e1c4be71
grand unified version numbers
...
Now the allmydata python package, the setup.py script, and the debian packages all get their tahoe version number from the same place.
2007-05-01 13:23:15 -07:00
f724719744
v0.2.0b1-0-UNSTABLE
2007-04-30 23:11:23 -07:00
e0a18d12af
globally search and replace "mesh" with "grid" and adjust description of the effect of NAT on the topology
2007-04-30 13:06:09 -07:00
b027ee1489
v0.1.4b2-0-UNSTABLE
2007-04-30 10:00:07 -07:00
7090ed66c5
v0.1.3-0-UNSTABLE
2007-04-30 06:02:43 -07:00
2fd7b81fba
v0.1.2-0-UNSTABLE
2007-04-29 23:00:08 -07:00
665b188af2
add licence, update metadata and URLs
2007-04-27 13:47:15 -07:00
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
dd4ad3d542
use pyfec instead of py_ecc for erasure coding and update API to codec
2007-02-01 16:07:00 -07:00
22e9e2eb0b
change build system to use subpackages pristinely and ask them to install themselves into an "instdir"
2007-01-30 14:57:59 -07:00
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
c94098b93a
split filetree_new.py up into smaller pieces, in a new subpackage
2007-01-17 13:54:38 -07:00
7a6bdadde5
add __init__ and setup.py glue for py_ecc, so we can import it
2007-01-01 23:43:24 -07:00
3490378551
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
8a3af8827a
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
aec1d1eecc
add bin/allmydata to create/stop/start nodes
2006-12-05 12:25:23 -07:00
97bdebd56e
setup.py: oops, add sub-packages, needed since I went back to distutils
2006-12-05 19:06:22 -07:00
aa943d4839
add distutils-based packaging
2006-12-05 01:29:26 -07:00
Brian Warner