[MacPorts] #18671: Can macfuse be upgraded to 2.0.3.2?

[MacPorts]

#18671: Can macfuse be upgraded to 2.0.3.2?
--------------------------------+-------------------------------------------
 Reporter:  other@…             |       Owner:  eridius@…           
     Type:  update              |      Status:  new                 
 Priority:  Normal              |   Milestone:                      
Component:  ports               |     Version:  1.7.0               
 Keywords:                      |        Port:  macfuse             
--------------------------------+-------------------------------------------

Comment(by dports@…):

 OK, here is my first take at a complete portfile patch for MacFuse 2.0.

 = Contents =

 This applies a few new patches:

  * files/patch-10.5-to-10.6.diff
  * files/patch-macfuse_buildtool.sh.diff
  * files/patch-sdk-objc_GMUserFileSystem.m.diff
  * files/patch-sdk-objc_MacFuse.xcodeproj.diff
 These four patch MacFUSE for 10.6 support -- the credit for these go to
 Jean-Luc Giraud, who did the bulk of the work. These patches should
 eventually be applied upstream. (Jean-Luc, have you submitted your changes
 to them?)

 files/patch-sdk-objc_MacFuse.xcodeproj.diff also patches it to build in
 ${workpath} instead of /tmp.


  * files/patch-10.4_libfuse_fuse-2.7.3-macosx.patch.diff
  * files/patch-10.5_libfuse_fuse-2.7.3-macosx.patch.diff
  * files/patch-10.6_libfuse_fuse-2.7.3-macosx.patch.diff
 These three (which are essentially the same path) are specific to
 MacPorts, and cause it to install into ${destpath} during build, making a
 separate destroot phase unnecessary.

 = Testing =

 I have tested these (using sshfs) on 32-bit 10.6. I expect that it should
 still work on 10.4 and 10.5 as well, but would appreciate it if someone
 with a 10.4 or 10.5 system handy could test it.

 I have not tested this on 64-bit yet and don't know what to expect. My
 '''''guess''''' is that the user-level libraries should build and work
 fine regardless of whether +universal is specified, but that the kernel
 module will only build 32-bit. According to
 [http://groups.google.com/group/macfuse/browse_thread/thread/97951b355e57db56
 this post], MacFUSE does not yet support 64-bit kernels. Feedback from
 anyone who tries this on 64-bit is especially appreciated; otherwise I'll
 see if I can borrow a 64-bit machine sometime soon.

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