tahoe-lafs/mac
Zooko O'Whielacronx 79fd1bd540 setup: remove binary _fusemodule.so 's
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/
2009-09-24 14:11:30 -07:00
..
fuseparts docs: Csaba Henk granted permission to license fuse.py under the same terms as Tahoe-LAFS itself 2009-09-21 08:46:59 -07:00
allmydata_tahoe.py macfuse: move macfuse files around to simplify pythonpath 2008-02-19 17:18:17 -07:00
allmydata.icns macapp: updated icon for mac build 2008-03-18 16:13:38 -07:00
COPYING.LGPL2 doc: add a copy of LGPL2 for documentation purposes for ubuntu 2009-09-23 22:42:18 -07:00
depends.py mac build: make a couple of build dependency hints soft imports 2008-02-26 17:39:07 -07:00
fuse.py docs: Csaba Henk granted permission to license fuse.py under the same terms as Tahoe-LAFS itself 2009-09-21 08:46:59 -07:00
Makefile fuse/impl_c: move mac tahoefuse impl out into contrib/fuse 2008-09-24 18:42:14 -07:00
README.txt docs: add mac/README.txt to explain the first few basic facts about what the files are in this directory 2009-02-07 16:33:21 -07:00
setup.py setup: the mac-exe build (using py2app) requires macholib>=1.2. 2009-07-03 10:57:02 -07:00

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