mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2024-12-28 16:58:53 +00:00
79fd1bd540
I would prefer to have just source code, or indications of what 3rd-party packages are required, under revision control, and have the build process generate or acquire the binaries as needed. Also, having these in our release tarballs is interfering with getting Tahoe-LAFS uploaded into Ubuntu Karmic. (Technically, they would accept binary modules as long as they came with the accompanying source so that they could satisfy their obligations under GPL2+ and TGPPL1+, but it is easier for now to remove the binaries from the source tree.) In this case, these modules come from the MacFUSE project: http://code.google.com/p/macfuse/ |
||
---|---|---|
.. | ||
fuseparts | ||
allmydata_tahoe.py | ||
allmydata.icns | ||
COPYING.LGPL2 | ||
depends.py | ||
fuse.py | ||
Makefile | ||
README.txt | ||
setup.py |
2009-02-07: Zooko wrote this what is in this directory after asking RobK about it: wxpython trappings to build a .app bundle which is both a gui app and (when launching the binary from within the .app bundle) a functioning bin/tahoe binary including "tahoe fuse" subcommand