Trouble with sshfs, caused by macfuse
Damien Clauzel
Damien at Clauzel.nom.fr
Thu Aug 13 08:09:41 PDT 2009
When installing the sshfs port, MacPorts wants first to install
macfuse as it is a dependance. Fine.
The problem is that when MacFuse is already installed through the
preference panel from Google (http://code.google.com/p/macfuse/).
The result is an error :
___
---> Activating macfuse
DEBUG: Image error: /Library/Filesystems/fusefs.fs/Contents/Info.plist
already exists and does not belong to a registered port. Unable to
activate port macfuse.
while executing
"_activate_contents $name $imagefiles $imagedir"
(procedure "portimage::activate" line 56)
invoked from within
"portimage::activate $portname [composite_version $portversion [array
get variations]] [array get options]"
Error: port activate failed: Image error: /Library/Filesystems/
fusefs.fs/Contents/Info.plist already exists and does not belong to a
registered port. Unable to activate port macfuse.
___
MacFuse cannot be activated, because the filesystem module is already
provided by Google's preference panel.
By consequence, sshfs cannot be installed because the macfuse port is
not activated, although FUSE support is correctly provided.
I can see 2 solutions for this :
1) remove macfuse dependance from sshfs : possible, but not ideal
because sshfs wouldn't be working
2) create a placeholder macfuse port, that would represent the fact
that MacFuse is already present on the computer
Any comments ?
Damien
More information about the macports-users
mailing list