Trouble with sshfs, caused by macfuse

[Brandon Allbery]

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.

-- 
brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com
system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu
electrical and computer engineering, carnegie mellon university    KF8NH



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090814/0296a4dc/attachment.bin>