site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Ryan McGann <rmcgann@mac.com> wrote: I have an application that needs a support folder in /Library/ Application Support. This folder is created when my installation package is run and has the following permissions: drwxrwxrwx 6 root admin 204 Aug 10 18:09 Foo When running the 10.6 upgrade to Snow Leopard from 10.5, the permissions get changed to: drwxr-xr-x 6 root admin 204 Aug 10 18:09 Foo This has the side effect of preventing the application from writing to the folder when run as a user other than root. Changing the permissions back to drwxrwxrwx after the upgrade fixes the problem, but I'd rather release a preemptive patch to fix this rather than dealing with it on the customer support side. Any suggestions? You can try storing your data in in /Users/Shared instead of Application Support. I'm not sure what the official recommendation is, but I'd take Apple changing the permissions behind your back as an unofficial recommendation, since it's obviously too late for them to change. ...note the section titled "Don’t Pollute User Space": Don _______________________________________________ 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... Ryan My two previous responses were bounced since my iPhone apparently can only send from my @me.com account but not from my subscribed @mac.com account. Listmom: should I unsubscribe/resubscribe? I commented that HOBOware (an application used by one of my clients to monitor/trend the temperature, humidity, etc., of their art storage areas) has the same issue. It was designed to be installed for a single user (it installs into ~/Library/Application\ Support), and assumed the user has admin rights. After discussions with the developer going over our managed environment (users are non-admins, AD/OD golden triangle environment), we came up with a solution that would allow the installer to put its stuff into the /Library/Application\ Support folder, then a login script would kick in once per user to copy stuff from /Library/ Application\ Support/HOBOware/ directory into the users' ~/Library/ Application\ Support/HOBOware/ folder so the application would reference the "user" domain data (the script would then delete itself). HOBOware obviously needs to be rewritten to respect/adhere to the Apple software distribution guidelines. Note how /Users directory (and /Users/Shared) should not be used for installs: http://developer.apple.com/documentation/MacOSX/Conceptual/BPFileSystem/Arti... /apple_ref/doc/uid/TP40001411 http://developer.apple.com/documentation/MacOSX/Conceptual/BPFileSystem/Arti... /apple_ref/doc/uid/TP40001411-111946 PS, thanks to the folks on this list (and a couple others) for the login script workaround. :) This email sent to site_archiver@lists.apple.com