Hi: Will it be possible to avoid installing the SDK? I'm sure the end users won't need the same install the developers will - or will they?
On Dec 6, 8:50 am, Jeff Mancuso <[email protected]> wrote: > Jason - > Basically, the update engine will ensure your users are always > installing the latest stable version available. It runs as part of the > MacFUSE installer package and is pretty transparent. > > If you're installing your application via Package Manager, you'll > likely want to crate a mpkg and add the MacFUSE package in. Be sure > that it PackageManager doesn't rename the package or modify the bundle > ID in the process - Package Manager on 10.5 performs all sorts of > unclean behavior, in my experience. You need to be careful to get the > package in there unmodified. > > Another option is to keep the MacFUSE package in your application's > bundle and run it [if needed] at first run, prompting the user for > their admin password, letting them know what you're doing.. > > Does this help? > -Jeff > > On Dec 1, 9:00 pm, Jason8 <[email protected]> wrote: > > > hi: > > > I'm looking for some high level guidance on how to use the > > "lightweight but sophisticated install/update engine" in a packaged > > install. I'm going to be deploying my file system via a package and > > will need to install MacFuse at some point along the way. > > > The Plan: > > I will add this tool to my package and use an AppleScript to wrap it > > and run it as a pre-condition. Once it finishes, I can then install my > > components. > > > Thanks in advance. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
