[MacPorts] #20176: Make the macfuse port play well with other macfuse installations

[MacPorts]

#20176: Make the macfuse port play well with other macfuse installations
----------------------------------+-----------------------------------------
 Reporter:  registrera@…          |       Owner:  eridius@…           
     Type:  request               |      Status:  new                 
 Priority:  Normal                |   Milestone:                      
Component:  ports                 |     Version:  1.7.1               
 Keywords:                        |        Port:  macfuse             
----------------------------------+-----------------------------------------

Old description:

> 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 [http://code.google.com/p/macfuse/wiki/AUTOINSTALL 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
> [http://groups.google.com/group/macfuse/browse_thread/thread/0de8694e951b42ee/4692acf60ac8adc9?#4692acf60ac8adc9
> 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".
>

> Regards
>
> /Daniel

New description:

 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 [http://code.google.com/p/macfuse/wiki/AUTOINSTALL 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
 ([http://groups.google.com/group/macfuse/browse_thread/thread/0de8694e951b42ee/4692acf60ac8adc9?#4692acf60ac8adc9
 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".


 Regards

 /Daniel

--

Comment(by macsforever2000@…):

 OK, I moved the second link to hopefully a more appropriate place.

-- 
Ticket URL: <http://trac.macports.org/ticket/20176#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS