site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On jeudi, février 8, 2007, at 10:42 AM, Bill Coderre wrote: [...] After all that, I forgot to tell you how to make an alias. This basically boils down to a simple idea: ln -s /path/to/MyApp.app ~/Desktop/Myapp.app [...] Note: ----- _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... Don't make an alias. Make a symlink instead. The end user will not see a difference between the two, and the symlink is MUCH simpler to make. (I see Stephane disagrees.... Well...) Hmm, I don't disagree, it's just that an Alias is more robust than a symlink. I do agree that it was much simpler to make a symlink. But it might not be too complex to make an alias with the tool I've just uploaded (source code + Xcode 2.4 project) at: http://s.sudre.free.fr/Software/HelperTools/bristow.zip (BSD License + the NDAlias License) usage: bristow [-a][-u] <file or directory> alias -a -- Install an alias in all users home folder. alias will be read as a relative path. -u -- Install an alias in the currently logged in user home folder. alias will be read as a relative path. It's using the SystemConfiguration framework to know the current logged in user and if the answer is "loginwindow" it does nothing. It's probably not working when using installer through a remote user session (such as ssh). It's using OpenDirectory to list all the "real" users (real means uid

=500, yes this can be wrong in some restricted cases such as setting a uid to less than 500 so that it does not appear in the Login window in list mode). This email sent to site_archiver@lists.apple.com