[MacPorts] #20176: Make the macfuse port play well with other macfuse installations
MacPorts
noreply at macports.org
Sun Sep 4 16:39:18 PDT 2011
#20176: Make the macfuse port play well with other macfuse installations
-----------------------------------+----------------------------------------
Reporter: registrera@… | Owner: dports@…
Type: enhancement | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 1.7.1
Resolution: wontfix | Keywords:
Port: macfuse |
-----------------------------------+----------------------------------------
Changes (by dports@…):
* status: new => closed
* resolution: => wontfix
Comment:
It's clear that there aren't going to be any future official releases of
MacFUSE, and we've switched to Fuse4X as the default for new installations
of fuse ports, so this seems moot now.
The fuse4x ports are better with respect to the issue described here.
Unlike the macfuse port, it doesn't install files outside of $prefix, and
won't install any files in the same place as the standalone installer, so
they won't try to overwrite each other's files. It's still the case that
only one kext version can be loaded, so there's a limit to how isolated
the two versions are, but things should work if both installations are of
the same version. It will also not conflict with a standalone installation
of MacFUSE.
--
Ticket URL: <https://trac.macports.org/ticket/20176#comment:17>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list