Where specific components of MacFUSE Core go should be knowledge internal to MacFUSE. It's not good to depend on the location of the kernel extension, etc., since you normally don't load the extension yourself.
Why not just look at /Library/Receipts/MacFUSE Core.pkg/Contents/ Info.plist and look for the version string in there? The probability of this location changing is far lower. Amit On Jun 6, 9:09 am, Jon Baer <[EMAIL PROTECTED]> wrote: > Hi, > > This upgrade is great, really appreciate your work (makes my life > easier) .. however it did "break" MacFusion 1.1 - my current GUI of > choice (in controller method checkForFuse() it looks for old > location), I read over some other posts here including how SSHFS is > unsupported, etc ... a question would be for 3rd party GUI developers, > could there be a standard way from ObjC to make sure it is installed > beforehand? (or is a check for NSString* fusePath = @"/System/ > Library/Filesystems/fusefs.fs/"; sufficient?) > > Thanks. > > - Jon > > On Jun 6, 12:22 am, Amit Singh <[EMAIL PROTECTED]> wrote: > > > I've finally gotten around to packaging this up. > > > Note that besides the custom volume icons feature, this release moves > > the kernel extension to live within the fusefs.fs bundle itself. > > Moreover, you will no longer be prompted to restart the system after > > an installation or upgrade. Read the changelog for details: > > >http://code.google.com/p/macfuse/wiki/CHANGELOG > > > Amit --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
