Loading Profile...
How can I use other filesytems than SFTP with ExpanDrive's version of FUSE?
I want to use FUSE for other things than SFTP, but ExpanDrive & MacFuse seem to be mutually exclusive, and I don't know how to use ExpanDrive's FUSE with other filesystems.
Also, is there a way to install Python bindings against ExpanDrive's version of FUSE?
It's very frustrating to have to choose between solid SFTP support and support for every other FUSE filesystem.
Also, is there a way to install Python bindings against ExpanDrive's version of FUSE?
It's very frustrating to have to choose between solid SFTP support and support for every other FUSE filesystem.
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?The current version of ExpanDrive installs MacFUSE version 1.7, exactly as found at the official MacFUSE site. It’s our intention to always have ExpanDrive install the most recent released version of MacFUSE.
You should be able to use any other MacFUSE file system while using ExpanDrive without issue. We try hard to make sure that if you install MacFUSE through ExpanDrive the installation ends up exactly the same as if you have used the MacFUSE installer itself. If you think there may be a problem with your MacFUSE installation, then I’d suggest you try uninstalling it, and then reinstalling it be hand from the MacFUSE installer.
You can uninstall MacFUSE by typing 'sudo /Library/Filesystems/fusefs.fs/Support/uninstall-macfuse-core.sh' on the command line in Leopard, or 'sudo /System/Library/Filesystems/fusefs.fs/Support/uninstall-macfuse-core.sh' on Tiger.
I’m happy
-
Inappropriate?Thanks for the quick reply!
I use MacPorts, and I guess what I really meant was that MacPorts's MacFuse seems to be incompatible with ExpanDrive.
I just now managed to download and install fuse-python 0.2 without using MacPorts and it works!
The trick is:
- Install pkgconfig (I used MacPorts to install)
- Temporarily modify /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pyport.h by commenting out the line "#include <osreldate.h>"
- sudo env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig python setup.py install
It's a messy mix of MacPorts, ExpanDrive, and hackery, though. If anyone knows of a cleaner way to do this, I'd love to hear it.
Thanks again.
I’m happy
3 Comments
Add a comment
This solves the problem
-
This is a great example of why the various Ports-style system of installing Open Source software are a bad idea. It's _always_ better to be using the standard distribution of an Open Source project, rather than getting it second-hand via MacPorts or Fink. -
Yes the hundreds of people who volunteer tens of thousands of hours to package software for operating systems so that it all works together as sanely and painlessly as possible are just wasting their time and mine.
?!! -
I didn't say there wasn't work in creating the Ports-style systems, just that the end user is better served by installing an Open Source project themselves, directly from the project, rather than depending on the third-party generated and maintained port to be (a) current and (b) compatible. As you yourself discovered with the MacPorts-based FUSE installation that generated your original problem and posting.
If all the people who contribute to the Ports were instead to contribute any compatibility issues and fixes _directly to the Open Source projects,_ then the projects would be improved directly, and in the right place: the projects themselves. If there's a reason why configure; make; sudo make install doesn't work on Mac OS X, then that should be fixed _in the Open Source project itself,_ not patched with a band-aid via MacPorts or Fink.
IMHO. YMMV.
EMPLOYEE
