[MacPorts] #29917: Fuse4X: add port
MacPorts
noreply at macports.org
Wed Jul 13 00:57:04 PDT 2011
#29917: Fuse4X: add port
--------------------------------------+-------------------------------------
Reporter: anatol.pomozov@… | Owner: dports@…
Type: submission | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port: fuse4x fuse4x-kext fuse4x-framework
--------------------------------------+-------------------------------------
Comment(by dports@…):
Replying to [comment:21 anatol.pomozov@…]:
> > I noticed the library installs as libfuse4x.dylib rather than libfuse
> The idea is to make fuse4x and macfuse coexist together on the same
computer.
I contemplated this one some more today and I'm undecided about whether
this is a good idea. For one, the benefit is illusory: macfuse and fuse4x
won't actually be able to coexist -- at least not in MacPorts, and
probably not with a standalone-installed version either -- because both of
them want to install `$prefix/include/fuse.h` in the same place.
It doesn't bother me so much that ports will need to know to link with
-lfuse4x instead of -lfuse, even though there are a couple that will need
to be patched. But it occurs to me that that does mean migrating from
macfuse to fuse4x would require rebuilding all installed filesystems just
to link them against a new library. If installing the library under the
same name meant that existing file systems would continue to work, that
would certainly be desirable.
Of course, all that is predicated on the library actually being ABI-
compatible with MacFUSE's libfuse! I imagine it is, but I haven't actually
checked.
--
Ticket URL: <https://trac.macports.org/ticket/29917#comment:38>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list