[MacPorts] #70000: macfuse @4.7.2: does not provide libosxfuse.dylib or libosxfuse_i64.dylib symlinks

[MacPorts]

#70000: macfuse @4.7.2: does not provide libosxfuse.dylib or libosxfuse_i64.dylib
symlinks
------------------------+------------------------
 Reporter:  ryandesign  |      Owner:  mohd-akram
     Type:  defect      |     Status:  assigned
 Priority:  Normal      |  Milestone:
Component:  ports       |    Version:  2.9.3
 Keywords:              |       Port:  macfuse
------------------------+------------------------
 The macfuse port installs libfuse.2.dylib and a libfuse.dylib symlink
 pointing to it so that one could use `-lfuse` to link with it. It also
 provides libosxfuse.2.dylib but it does not provide libosxfuse.dylib so
 that using `-losxfuse`, like [ticket:69997 ext2fuse does], fails:

 {{{
 % port installed macfuse
 The following ports are currently installed:
   macfuse @4.7.2_0 (active)
 % ls -l $(port contents macfuse|grep dylib$)
 -rwxr-xr-x  1 root  wheel  531568 Apr 27 16:47
 /opt/local/lib/libfuse.2.dylib
 lrwxr-xr-x  1 root  wheel      15 Apr 27 16:47
 /opt/local/lib/libfuse.dylib -> libfuse.2.dylib
 lrwxr-xr-x  1 root  wheel      15 Apr 27 16:47
 /opt/local/lib/libosxfuse.2.dylib -> libfuse.2.dylib
 lrwxr-xr-x  1 root  wheel      15 Apr 27 16:47
 /opt/local/lib/libosxfuse_i64.2.dylib -> libfuse.2.dylib
 }}}

 Is this intentional or could the port provide libosxfuse.dylib as well?

 Similarly it provides a libosxfuse_i64.2.dylib symlink but not a
 libosxfuse_i64.dylib symlink so if anybody tried to link with
 `-losxfuse_i64` that would fail.

-- 
Ticket URL: <https://trac.macports.org/ticket/70000>
MacPorts <https://www.macports.org/>
Ports system for macOS