site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Thanks, j On Aug 14, 2008, at 1:22 PM, Luke Bellandi wrote: On 8/14/08 9:56 AM, "Jeremy Matthews" <jeremymatthews@mac.com> wrote: Question - can we get packagemaker to respect the tilde-based path in component installation paths? Every time we tried it kicked it back...but this would be really nice for depositing user-specific files during an install. Thanks, jeremy On Aug 14, 2008, at 12:25 PM, Gignac, Jason (HAS-SAT) wrote: My pleasure. On 8/14/08 Thursday, August 14, 2008 -11:24 AM, "Jeremy Matthews" <jeremymatthews@mac.com> wrote: hmmm...interesting. Thanks! -j On Aug 14, 2008, at 12:23 PM, Gignac, Jason (HAS-SAT) wrote: On 8/14/08 Thursday, August 14, 2008 -11:20 AM, "Jeremy Matthews" <jeremymatthews@mac.com> wrote: Ideas? thanks, jeremy On Aug 14, 2008, at 12:18 PM, Gignac, Jason (HAS-SAT) wrote: Does the pref file you are writing to already exist or not? Hmmmm...even if we were writing to defaults to: /Library/Preferences/com.apple.xxx simplestring abc123 I get the user defaults thing - we can work around that. Thanks, jeremy On Aug 14, 2008, at 12:12 PM, Luke Bellandi wrote: Hi Jeremy, Best, Luke On 8/14/08 5:40 AM, "Jeremy Matthews" <jeremymatthews@mac.com> wrote: After doing some maintenance on my computer I noticed that simple shell scripts are now working (echo commands, etc) in packages - maybe those 3 developer packages needed some housekeeping... However, some of my other postinstall scripts don't execute (which I never tried before anyways); most of these write to user defaults, for example, registering Transmit: What are the known limits to postinstall scripts? Thanks, jeremy On Aug 13, 2008, at 5:39 PM, Gignac, Jason (HAS-SAT) wrote: On 8/13/08 Wednesday, August 13, 2008 -4:38 PM, "Stéphane Sudre" <iceberg-dev@orange.fr> wrote: On Aug 13, 2008, at 12:22 AM, Jeremy Matthews wrote: If you can provide a sample package illustrating the issue, this can help. As far as I can tell (from the documentation), postupgrade script are not supported by the FLAT package format. Adding one to the resources would not help. http://lists.apple.com/mailman/options/installer-dev/jason.gignac%40p ea rs on .c o _______________________________________________ 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/luke%40adobe.com _______________________________________________ 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... The issue would be that the installer runs as root, and not the user install it. We have user-based preference files... I'd suggest having the application write out all preferences. It's generally much better practice to have the application manage all preferences as opposed to having the Installer push defaults into place during installation. Apps can check for non-existent prefs on first launch and write them out then as necessary. You might try just putting a default pref file in the package, then writing, see if ti works. I've had mixed results with writing to nonexistent prefs files. Hmmm - some do and some don't. Normally, when you perform that kind of action, it will create the plist if not already there....unless you know something I have forgotten... On 8/14/08 Thursday, August 14, 2008 -11:17 AM, "Jeremy Matthews" <jeremymatthews@mac.com> wrote: IIRC, if when installing a package with Admin/Root privileges, these scripts are run as root user. In that case, any mucking with user- preferences will change the root user's preferences -- not the prefs of the user that launched the package. I'd check that out. ----- ## Licensing Transmit defaults write com.panic.Transmit3 SerialNumber XXXX-XXXX- XXXX- XXXX ----- That's correct, 'ccording to Apple, you just have the one pre and the one post script in a flat package. Since I got asked (more than once) about using postUPPGRADE scripts (not just postinstall), I assumed there was some bug in packagemaker that mean it was supporting those as a workaround for not supporting postINSTALL scripts. So, I had specified a postinstall script (per 10.5 - normal) as well as a directory containing a scripts "postupgrade". Of course, I tried builgind and installing packages with and without that option - nothing seemed to work. _______________________________________________ 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: m This email sent to jason.gignac@pearson.com _______________________________________________ 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/luke%40adobe.com This email sent to luke@adobe.com This email sent to luke@adobe.com This email sent to site_archiver@lists.apple.com