Trouble with sshfs, caused by macfuse

[Ryan Schmidt]

On Aug 14, 2009, at 15:48, Brandon Allbery wrote:

> On Aug 13, 2009, at 18:38 , Ryan Schmidt wrote:
>> On Aug 13, 2009, at 10:09, Damien Clauzel wrote:
>>> 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 ?
>>
>> By design, MacPorts does not use libraries already installed on  
>> your computer.
>>
>> http://trac.macports.org/wiki/FAQ#ownlibs
>>
>> The solution is to remove the MacFuse you already have and let  
>> MacPorts install it.
>
> So MacPorts is incompatible with Google Desktop (which requires  
> MacFuse 2.x).  Good to know before I get stuck.

Hmm. And I suppose Google Desktop can't use the MacFUSE installed by  
MacPorts? Or is that only because the version of MacFUSE in MacPorts  
is 1.7 and not 2.x? If so, the version of MacFUSE in MacPorts should  
be updated, and we do have a ticket for that request:

http://trac.macports.org/ticket/18671