I don't mean to sound abrupt, but I probably will since I'm very short on time right now.
You're only thinking of *your* potential nightmare, not my potential and *existing* nightmares. There are reasons for the 10.4/10.5 fork, and I'm afraid there won't be a single binary distribution or a unified trunk. Besides, there will be features that won't/can't be added to the 10.4 version of MacFUSE. Amit On Jan 16, 2:12 pm, Dave Koziol <[EMAIL PROTECTED]> wrote: > I'm working on add a MacFUSE file system to an existing end user > application, and one of the things that strikes me as a potential > support nightmare, is that there is a 10.4 and a 10.5 version of > MacFUSE. Some of my customers are going to be running 10.4, and > eventually some of them will upgrade to 10.5, and expect everything to > continue working. > > I did some diffs of the 10.4 and 10.5 directories and there don't > appear to be significant differences, so it would seem to be possible > to build a single version which works on both 10.4 and 10.5. I'm > curious why the code was branched, maybe I'm missing something, and > what the thoughts are on merging the two branches back into a single > unified trunk? > > Dave Koziol > Arbormoon Software, Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
