Ticket #30383 (closed defect: fixed)
fuse filesystems should support fuse4x as dependency
|Reported by:||dports@…||Owned by:||dports@…|
|Keywords:||Cc:||anatol.pomozov@…, darenzana@…, Markus.Ueberall@…, sfiera@…, raimue@…, mellon85@…, mail@…, petri@…, bonoba@…|
|Port:||bindfs curlftpfs encfs ext2fuse fuse-bindings-python fuse-bindings-python25 mhddfs mp3fs ntfs-3g procfs spotlightfs|
I just added ports for Fuse4X, a fork of MacFUSE that provides 64-bit kernel support among other features. It should be possible to use any of our existing fuse filesystem to run atop fuse4x, although macfuse should remain the default.
At a minimum, existing ports will need to change their port:macfuse dependency to path:lib/pkgconfig/fuse.pc:macfuse
Some other problems ports might run into:
- fuse4x's library is -lfuse4x not -lfuse; ports using pkgconfig should figure this out on their own
- macfuse includes emulation of named semaphores, fuse4x doesn't
- fuse4x's framework is in a different location (and in the fuse4x-framework port)
I am looking through the ports now to see if they work with fuse4x, and will report here if any changes seem to be necessary. I already fixed sshfs in r81150.
- Port changed from bindfs curlftpfs encfs ext2fuse fuse-bindings-python fuse-bindings-python25 gmailfs mhddfs mp3fs ntfs-3g procfs spotlightfs to bindfs curlftpfs encfs ext2fuse fuse-bindings-python fuse-bindings-python25 mhddfs mp3fs ntfs-3g procfs spotlightfs
comment:14 Changed 5 years ago by dports@…
- Status changed from new to closed
- Resolution set to fixed