At http://groups.google.com/group/macfuse-devel/msg/3a2c6ef2c197d88e on 16th June:
> At 7:21 PM +0000 6/9/07, Amit Singh wrote: > >> If people use alternate packagings of *MacFUSE Core*, that makes it >> unnecessarily harder, and impossible in some cases, for me to offer >> them support. I have not seen any convincing or justifiable arguments >> in favor of using arbitrary packagings. Some features might not even >> work if you move things around (the file system bundle has to be in a >> specific location). Unlike programs or libraries, MacFUSE Core is a >> global system-shared resource that you can't have multiple instances >> of. > > FWIW, I use MacFUSE from Fink because I can upgrade 4 systems > at once (2 at work & 2 at home), without ARD or any special tricks. > > I will switch to MacFUSE Core if I have serious trouble with > Fink's build, but so far it's done what I want. > > Regards, > > Chris > -- > Chris Pepper: <http://www.reppep.com/~pepper/> > <http://www.extrapepperoni.com/> > The Rockefeller University: <http://www.rockefeller.edu/> By coincidence, on the same day at http://www.dur.ac.uk/durmac/forum/read.php?4,593,611#msg-611 > ... what might be useful is if a tool could be created to enable > universities to package MacFuse components (the core, and the SSH file > system component) into a single installer/executable with specific > settings for their particular institution ... In the Durham University thread I have linked to some MacFusion- related thoughts/issues. A few weeks ago I was thinking about metapackages. Primarily because I someimtes use Apple Remote Desktop for installations, and whilst using ARD I'm more comfortable with .pkg and .mpkg. > upgrade 4 systems at once That's certainly appealing. I'm not a scripter but I guess that without investing in ARD, a shell script .command could: a) copy the required metapackage (or packages) to destinations, then b) run installer http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/installer.8.html to perform the installations. At the remote destinations, /private/tmp should be a fine temporary location for packages. (ARD 2 copies packages to /private/tmp/ARD_PKG_ITEMS drwx------ 3 root wheel 102 Jun 17 15:22 ARD_PKG_ITEMS prior to installation, installs, then removes the directory.) Whether a script could perform such installations _concurrently_, I don't know. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
