sshfs @2.2_1: New variant to use fuse4x instead of the defunct macfuse

[david@…]

The macfuse port doesn't install on OS X Lion, and the macfuse project seems to be abandoned since December 2008. Its successor seems to be fuse4x. This variant allows the sshfs port to depend on the fuse4x port instead of macfuse (in fact you could make this the default option).

[ryandesign (Ryan Carsten Schmidt)]

There is no need for a variant. Simply install fuse4x first. Then install sshfs (or any other port that depends on macfuse). Perhaps later we'll change the default for these ports from macfuse to fuse4x.

[david@…]

Cool, thanks. So that's what the depends_lib path:lib/pkgconfig/fuse.pc:macfuse in the Portfile means -- to install macfuse only if fuse.pc isn't present.

It would be awesome if the UI reflected this reality: port deps sshfs currently lists macfuse, even when the fuse4x port is installed. Implementation details could get tricky -- would you want macports to track down which port provided fuse.pc, and list that one in the dependencies instead?

[anatol (Anatol Pomozov)]

The plan indeed is to abandon macfuse port and make fuse4x as a default Fuse API implementation. But fuse4x port is young - we need more testing (even despite the fact that the project is based on macfuse).

I compiled and tried to use fuse4x with all filesystems in macports (except procfs and spotlightfs) and it seems works fine. Please use fuse4x and provide feedback about it, either positive or negative - it'll make the decision making faster.