I have. And if I'm lucky I'll be able to dig up the code :) On Mon, Apr 18, 2011 at 4:09 PM, Benjamin Fleischer <[email protected]> wrote: > Hi, > I created a github repository a week ago. I used Erik's locking code and > modified the prefpane/updater to check my github page for macfuse updates. > If anyone is interested you can find my repository at > http://github.com/bfleischer/macfuse > In the "tools" directory is a shell script named "key_generator" which > generates a new rsa key pair (and the C array representation of the public > key) needed to sign macfuse releases. > At the moment I'm trying to port the newest libfuse release 2.8.5. Has > anyone attempted this before? > Regards > Benjamin > Am 18.04.2011 um 15:53 schrieb Tomas Carnecky: > > I've created a MacFUSE organization on github. I'm in the process of > importing the old code from the svn repo into git, I just need to > collect the identities of the original contributors so I can do a > proper conversion. After that I plan to collect all the different > branches and patches that have been floating around and then we'll see > how to go from there. Does that sound like a plan? > > On Sat, Apr 16, 2011 at 7:21 PM, Anatol Pomozov > <[email protected]> wrote: > > +Amit and some people from macports > > Hi, Amit. > > Taking into account the current situation are you willing to transfer > > the project ownership to someone else? There are few candidates for > > this position. Some of them: maintainers of macports project, authors > > of existing forks, or maybe you have a candidate that is interesting > > in maintaining the project. > > I think that macfuse project is too important to let it die. The are a > > lot of active macfuse users, many people use it via macports. Macfuse > > really needs some owner/maintainer. And for beginning it worth > > consolidating a bunch of patches from third-party forks and macports > > (https://trac.macports.org/browser/trunk/dports/fuse/macfuse/files). > > Is there any chance that you add someone as a developer/owner to the > > googlecode project? Of course there is always possible to fork the > > project and put it to github, but I think it would be much better for > > the macfuse community to continue development at the existing > > location. > > Amit, what do you think? > > On Sat, Apr 16, 2011 at 3:38 AM, Jonathan Morgan > > <[email protected]> wrote: > > Indeed there are several forks that have developed 64bit versions due to the > lack of central administration of the project on this thread / Goggle. It's > a real shame, and I for one would be very willing to get behind a new branch > on github (for instance). We (at Object-Matrix.com) use MacFUSE, Fuse and > JDokan (Windows equivalent, strangely better supported) together with JFuse > for a core product, other significant companies, e.g., Wuala also seem to > use it judging by their posts. I'm sure that the community will get the > product working on Mac Lion, but some consensus on the best organised fork > to follow/submit to would be excellent. > > You could also look at KFS. > > > On 16 Apr 2011, at 00:23, [email protected] wrote: > > Hi, > > I was trying to use macfuse from macports on my 10.6.4 x64. It looks like it > (fuse_mount/fuse_new functions) does not work. I decided to go to the > official site to check issues list and find something similar. Then I came > to this maillist. > > What I found: > > - last release has been made 3 years ago > > - last source change has been made 2 years ago > > - the original author says that he has no time to work on the project > anymore > > - there are 2 other forks that make macfuse work on latest MacOSX (include > 64bits version) > > - nobody else has development access to repository so nobody can submit > fixes from contributors > > - there are 2 forks on github > > For me it clearly says that the project is dead now. There are few questions > here: > > - is anybody going to continue this project? At least on github. > > - if not is there any alternative to macfuse? I would like to use fuse for > my cross-platform application. The app works fine on Linux, I am trying to > port it macosx. > > -- > > 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. > > -- > > 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. > > > > -- > > 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. > > > > -- > 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. > > > -- > 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. >
-- 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.
