> A new official release? As the current HEAD is the same as tuxera repo > the new release will be the same as 2.1.9.dmg The reason I want it is > to force macports to move to it. So macports either abandon their > changes or move it upstream. This way we remove yet another source of > confusion.
You seem to focus solely on MacPorts. What about the regular MacFUSE update mechanism (PrefPane)? The PrefPane in the official MacFUSE SVN is broken. Therefore I fixed it last October when I released a patched version of MacFUSE 2.1.7 using Erik's early stage locking code to get this thing working with 64 bit kernels. If anyone is interested in this you can find my work at https://github.com/bfleischer/macfuse in branch macfuse-2.1. My latest stable binary release (2.1.11) is based on the latest modifications from Tuxera (2.1.9) and can be found at http://bfleischer.github.com/macfuse/. By the way, the patched up PrefPane checks this github-page for updates, too. > A few mid-term tasks: > * update fuse to 2.8.5. Currently macfuse depends on horribly outdated > 3 yo libfuse release. As I wrote a few weeks back I'm in the progress of patching fuse-2.8.5 in order to work with MacFUSE. I made some progress and have a version that compiles fine (with my source release and using the 10.6 SDK rather than 10.5 as Tuxera does) but there seems to be some incompatibilities regarding the kernel interface. fuse 2.8.5 uses interface version 7.12. MacFUSE currently only supports 7.8. My fuse repository can be found at https://github.com/bfleischer/fuse/ It contains the original fuse 2.8.5 source in branch fuse-2.8.5 and the patched (but far from stable) version in branch fuse-8.8.5-macfuse. Help is always welcome. A script to create a patch that plays well with the MacFUSE buildtool can be found in branch tools. > * create a fork of libfuse and sshfs repositories. Currently diffs > between upstream and macfuse changes is stored as a patch. > https://github.com/macfuse/macfuse/tree/master/core/10.5/libfuse It is > ugly. Especially if you want to look diff over diff. Instead we should > have separate repos with 2 branches - upstream and macfuse. When you > make a change to libfuse repo - you update the diff as well. Or even > better - to remove *.patch files at all and just use git submodules. I would suggest one step after another. For now most MacFUSE code bases are still somewhat similar. If you start changing stuff like this right now we might get more problems than it is worth. Just my opinion. Another reason for the .patch file might be the different license model. MacFUSE uses a BSD style license whereas fuse uses GPL and LGPL. This keeps the cut clean. -- You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/macfuse?hl=en.
