Re: Can I refer to files outside of a .pax archive?
site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On jeudi, juin 29, 2006, at 11:30 PM, Rick Sustek wrote: 1. Permissions issue to drop the file(s) 2. Permissions are blown up if an admin user do this 3. An alias speaks only one language 4. Window Background pictures are not localizable ----- Point 2: Nobody ever cares. Point 1: Nobody ever cares. Any OS X user is an admin user, right? My €0.02 _______________________________________________ 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... For the simple drag install, I definitely like the popular convention of placing an alias to the /Applications folder right next to the icon of the app itself, and indicating that the user should just drag it over. Some reasons why this technique is a potential source of problems even when it seems just brilliant: One needs to be user with Admin privileges to do this (unless the permissions have been blown away by previous installations, which is not an uncommon situation in Mac OS X). So users with no admin accounts will try to drag and drop the file(s) and it won't work. Yet they were instructed to do that. The owner of the dropped files become the admin user who dropped the file not root as it should be. It might not be an issue but next time someone runs a Repair Permissions after installing an OS update (as if the problem was not there before the update), he may see that the permissions were incorrect and doesn't remember he just drag and dropped the file. It might be nice to have an alias of the Applications folder but Applications is not spelled "Applications" in Japanese. So one's potential Japanese customers will wonder what Applications is supposed to mean. Let's omit the fact that Finder Window Background pictures set on Mac OS X 10.2 and later are not visible on Mac OS X 10.1. If they are not localizable, then it means you need to make one version for each language you're supporting so that the instructions do not turn into an enigma. The QA team (just in case you're not the QA team too) will thank you for adding more testing cases. Advantage: it solves Point 3. Based on the different applications installed by drag and drop from a disk image I've seen: Points 3 and 4: Never taken into account. The application is touted to include a bunch of localization, but the installation procedure is not localized itself. This email sent to site_archiver@lists.apple.com
participants (1)
-
Stéphane Sudre