Hi On Thu, May 5, 2011 at 11:06 AM, Benjamin Fleischer <[email protected]> wrote: > You seem to focus solely on MacPorts. I use macfuse mostly as a library from macports so it is not a surprise that I care about this part a lot.
I am glad to hear that there are people who care about other parts of the project. > 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. Great to hear it! May I ask you to send the fix as a commit based on the current HEAD? https://github.com/macfuse/macfuse/ PrefPane fix is definitely worth submitting to the upstream. > 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. It makes sense. Consolidating all patches and fixes is more important task. > 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.
