Folks: When we release Tahoe-LAFS v1.8.1, I would really like it if people who try to install it, following quickstart.html [1], succeed even if they don't have a full development environment with a compiler, Python header files, and libs like OpenSSL. They can do so if there are binary packages of all of the deps, which we host here:
http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html (and also we need to fix ticket #1233) Please inspect that README.html and determine whether your favorite platform has binaries of each of the dependencies. If there is a missing binary package, you can build it on your system by acquiring a source distribution of a recent release and running "python setup.py bdist_egg". Then give us the resulting .egg file to host on tahoe-lafs.org. Thanks! Also, if you want to contribute a patch to the script that generates this README.html, it is in misc/build_helpers/gen-package-table.py . Please change it to have a separate table for each version of Python and within each table make the columns be the dependencies and the rows be the platforms. This will make it easier for people to see which packages are available on their platform. Regards, Zooko http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1233# prefer binary eggs which satisfy dependencies over source eggs which are even newer [1] http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.html [2] http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/misc/build_helpers/gen-package-table.py _______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
