Ticket #20176 (closed enhancement: wontfix)
Make the macfuse port play well with other macfuse installations
|Reported by:||registrera@…||Owned by:||dports@…|
|Keywords:||Cc:||macports@…, ask@…, eridius@…, julien.cornebise@…|
Description (last modified by macsforever2000@…) (diff)
The kernel extension of macfuse is installed outside the "isolated" environment of macports and conflicts with other installations of the same kernel extension. Since the version provided by macfuse is lagging a few versions behind it is becoming difficult to use the macfuse-dependent ports simultaneously with non-port fuse-filesystems.
The recommended way to keep Macfuse up to date is through the official automatic updater. But at least the mp3fs-port doesn't work if other applications use the automatic updater and replaces the kernel extension.
Maybe it would be possible to include the automatic updater in the port? Or maybe it would be better to just wrap the official installer with a port and link to the headers and lib-files for dependent ports to use (suggested a long time ago by a Macfuse developer)?
I have temporarily solved my own problems (getting mp3fs-port to work with official Macfuse-install) by symlinking /opt/local/include/fuse to /usr/local/include/fuse (created by official installer) and each libfuse* in /opt/local/lib to the corresponding file in /usr/local/lib
I'm not capable of determining which is the best approach, or if there are any side effects of my own attempt to solve this. All I can say is that it would be great if "it just worked".
comment:13 Changed 3 years ago by jmr@…
- Cc eridius@… added; dports@… removed
- Owner changed from eridius@… to dports@…