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/

diff --git a/mac/10.4/fuseparts/_fusemodule.so b/mac/10.4/fuseparts/_fusemodule.so
deleted file mode 100644 (file)
index c802be4..0000000
Binary files a/mac/10.4/fuseparts/_fusemodule.so and /dev/null differ

diff --git a/mac/10.5/fuseparts/_fusemodule.so b/mac/10.5/fuseparts/_fusemodule.so
deleted file mode 100644 (file)
index 04efd0d..0000000
Binary files a/mac/10.5/fuseparts/_fusemodule.so and /dev/null differ