le 26/03/06 17:47, Thom McGrath <[EMAIL PROTECTED]> a écrit : > When it comes time to auto-update, the app downloads the exact same > file as a new user would. It then mounts the disk image, renames > itself to <app name>.old while running (it works), copies the new > version into the same directory, unmounts the image, throws it away, > launches the new version, then quits itself. Because an app cannot > delete itself, the new app looks for the old copy and will delete it > at launch. The process works completely automatically, no user > interaction at all (except, of course, the user accepting the new > version).
If the user have an alias file (Dock or anywhere else), is the link still valid after the update ? François Van Lerberghe Rue Thier Monty, 15 A 4570 Marchin Belgique _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
