September 2007 - Installer-dev

Re: Distribution script format second (stupid) question
by Stéphane Sudre 06 Sep '07

06 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On mardi, septembre 4, 2007, at 09:39 PM, Peter Bierman wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… <installer-gui-script> was the element name initially, but was simplified to <installer-script> before 10.4 went GM. Unfortunately, a lot of Apple software is built from templates, and things that aren't actively broken are low on the priority list for fixing. Then the templates get copied, and things like this linger for years. Well, maybe it will bee sooner than later since I filed a bug report against it... But having seen bug reports in some parts of the OS being addressed more than 3 years after their submission, I don't have great expectancies though. This email sent to site_archiver(a)lists.apple.com

1 0

Support 10.3 option
by annette.brooks＠myob.com 06 Sep '07

06 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com I used the assistant to create a metapackage and checked the "Support 10.3 and 10.2 option". I am now trying to support those same OS's in another install - but can't figure how to do it without using the assistant. Even in the meta I created I don't see any script that was created to do a volumecheck. Also - I know a log is created SOMEWHERE after an install is run - can anyone tell me where it is located?? _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Dynamic Install Location?
by Nigel Kersten 06 Sep '07

06 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Dynamic Install Location?
by Bill Coderre 06 Sep '07

06 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Distribution script format second (stupid) question
by Peter Bierman 04 Sep '07

04 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com -pmb <installer-script> Yet, iWork '08 (among other Apple products) uses: <installer-gui-script> Bug filed in Radar. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/bierman%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… <installer-gui-script> was the element name initially, but was simplified to <installer-script> before 10.4 went GM. Unfortunately, a lot of Apple software is built from templates, and things that aren't actively broken are low on the priority list for fixing. Then the templates get copied, and things like this linger for years. <installer-script> is the correct element name. There's no difference between them. At 11:51 PM +0200 9/1/07, Stéphane Sudre wrote: According to the documentation (release notes), Distribution scripts root tag is: Is there supposedly a difference between them (such as an installer-gui-script can't be run through the installer command tool)? This email sent to bierman(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Dynamic Install Location?
by Nigel Kersten 04 Sep '07

04 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Sep 4, 2007, at 10:07 AM, Fritz Anderson wrote: On Sep 4, 2007, at 11:12 AM, Nigel Kersten wrote: On Sep 4, 2007, at 8:31 AM, Nigel Kersten wrote: So currently I'm using the method of a preflight script that: * retrieves the ruby sitelibdir parameter * removes /tmp/my-symlink * symlinks sitelibdir at /tmp/my-symlink * package destination is set to /tmp/my-symlink with follow symlinks on. I was also thinking about whether I could get an mpkg preinstall to modify the install location for one of it's containing pkgs. Scratch that one off the list. It doesn't work unfortunately. I can modify the Info.plist of the sub-pkg with a preflight in the mpkg, but it doesn't get picked up, as they must all get parsed before the preflight runs. It works happily the second time you install the pkg, so I guess I could make an empty pkg that modified another pkg plist and installed it as part of one of the scripts, but that's not a particularly pleasant feeling workaround. Even if it "worked," it wouldn't work when (not if) you distribute your installer on read-only media. Excellent point, and one I'd definitely forgotten, even though it's not going to apply in this case. (pkgs are being installed via a remote management system and aren't being distributed in a read-only format) Is this really the best option for doing this? It annoys me that I then don't get to observe the full paths with lsbom once the package is installed. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Dynamic Install Location?
by Fritz Anderson 04 Sep '07

04 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Sep 4, 2007, at 11:12 AM, Nigel Kersten wrote: On Sep 4, 2007, at 8:31 AM, Nigel Kersten wrote: — F _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I was also thinking about whether I could get an mpkg preinstall to modify the install location for one of it's containing pkgs. Scratch that one off the list. It doesn't work unfortunately. I can modify the Info.plist of the sub-pkg with a preflight in the mpkg, but it doesn't get picked up, as they must all get parsed before the preflight runs. It works happily the second time you install the pkg, so I guess I could make an empty pkg that modified another pkg plist and installed it as part of one of the scripts, but that's not a particularly pleasant feeling workaround. Even if it "worked," it wouldn't work when (not if) you distribute your installer on read-only media. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Dynamic Install Location?
by Nigel Kersten 04 Sep '07

04 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Sep 4, 2007, at 8:31 AM, Nigel Kersten wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I was also thinking about whether I could get an mpkg preinstall to modify the install location for one of it's containing pkgs. Scratch that one off the list. It doesn't work unfortunately. I can modify the Info.plist of the sub-pkg with a preflight in the mpkg, but it doesn't get picked up, as they must all get parsed before the preflight runs. It works happily the second time you install the pkg, so I guess I could make an empty pkg that modified another pkg plist and installed it as part of one of the scripts, but that's not a particularly pleasant feeling workaround. This email sent to site_archiver(a)lists.apple.com

1 0

Dynamic Install Location?
by Nigel Kersten 04 Sep '07

04 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Suggestions I've seen have been: Surely this must be a well solved problem? _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… So I've been browsing the archives and have seen this question asked a few times, with several different answers.... What's the best way to dynamically set the install location for a pkg? I have a pkg I'm putting together that needs to be installed into $RUBYLIB, which may be in different locations depending upon the client environment. * Installer Plugins * preflight script that symlinks desired destination to the hardwired destination (ie, ln -s $RUBYLIB /tmp/somepath) * postflight script that copies payload to the desired destination. * locator definitions, which to be honest I don't quite get yet. I was also thinking about whether I could get an mpkg preinstall to modify the install location for one of it's containing pkgs. This email sent to site_archiver(a)lists.apple.com

1 0

Distribution script format second (stupid) question
by Stéphane Sudre 01 Sep '07

01 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com <installer-script> Yet, iWork '08 (among other Apple products) uses: <installer-gui-script> Bug filed in Radar. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… According to the documentation (release notes), Distribution scripts root tag is: Is there supposedly a difference between them (such as an installer-gui-script can't be run through the installer command tool)? This email sent to site_archiver(a)lists.apple.com

1 0