October 2009 - Installer-dev

Re: Missing install receipt and script parameter in Snow Leopard
by Jim Dodd 15 Oct '09

15 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1255620384; bh=f50c/vdAbmzMi/s3b4/08coxw8FJtD28/OKl+Qz+r28=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=F0LrtuMOsINkYPfNI5Ildu2zD+7TIwfmP2+Tb2nukGFAwAASoQ0ngYGxVb23mcoyo0KVf58wSVGnMtbr8604uIHB4qsIjOuIu/Qo1XhP69VVpqXr+/vBSlTOL32qpcCljEr9pzJ539drAHAB7AZ4l2jCdGZW4GTx82HpDd1sJlA= Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=URsjxzS0M9PqDNhNExstHPNhBXDUNC7qPJ/mHiNAP30G4R5jZK5l0srWn53f/TJY8NL+HLnaClBnqbL5h+GdftrLpaHdx9NovU3TyL028pQ5Og31aCg8hK/bJCKXMoFBXqaotW/P2FHCudJyixLJrLU+C151yb+rjMt7i7v/PtE=; Thank you, Allen. Not only did they move the receipts folder, they've changed what is saved there. No longer is the PKG files saved there but now there are two different files. A BOM file (looks like the BOM from the installer package) and a PLIST file with information about when, where and what was installed. So that's why I could never find it when I searched. You saved me a lot of trouble. And by removing those files, I was able to test the difference between install and upgrade scripts. Here's what I found. The preinstall, postinstall and postupgrade scripts only receive three parameters from the installer under Snow Leopard. The preupgrade script receives four parameters from the installer just as all scripts did in previous releases of OS X. I don't know whether the third parameter (the installation volume or mountpoint to receive the payload) or fourth parameter (root directory of the system) are missing from the calls because in every case I've seen, they are both just "/". Perhaps Apple would like to comment on which one is missing and why we wouldn't need that information. I am amazed they would just change the number of parameters like that. I will be entering this as a bug at bugreporter.apple.com. Thank you again, Allen. Regards, Jim Dodd Onset Computer Corporation ----- Original Message ---- > From: "Riffel, Allen" <ARiffel(a)extensis.com> > To: Jim Dodd <bcbuilderboy(a)yahoo.com>; Installer-dev(a)lists.apple.com > Sent: Thu, October 15, 2009 10:41:14 AM > Subject: RE: Missing install receipt and script parameter in Snow Leopard > > In Snow Leopard they were nice enough to move the receipts folder to: > /private/var/db. Also, the receipts folder in that directory is all > named with lower case characters: "receipts". > > Allen Riffel > QA Engineer > Extensis > http://www.extensis.com/ > phone: 503.274.2020 x116 > email: ariffel(a)extensis.com > > Font and Creative Assets Management Software. Trusted by Millions. > > To learn more about Extensis Solutions, visit: > http://www.extensis.com/en/solutions/index.jsp > > Notice: This communication may contain privileged or other confidential > information. If you are not the intended recipient, or believe that you > have received this communication in error, please do not print, copy, > retransmit, disseminate, or otherwise use the information. Also, please > indicate to the sender that you have received this email in error, and > delete the copy you received. Thank you. > > -----Original Message----- > From: installer-dev-bounces+ariffel=extensis.com(a)lists.apple.com > [mailto:installer-dev-bounces+ariffel=extensis.com@lists.apple.com] On > Behalf Of Jim Dodd > Sent: Thursday, October 15, 2009 07:31 > To: Installer-dev(a)lists.apple.com > Subject: Missing install receipt and script parameter in Snow Leopard > > I have an installer package that runs on both Leopard and Snow Leopard > successfully. There are three problems, though: > > 1) For Snow Leopard, I had to modify our postupgrade script to deal with > a missing parameter passed to the scripts by the Installer.app. I do not > know if it is the third or the fourth parameter that is missing. All I > know is they have been there in all other versions of OS X and now they > are not. There are four parameters passed to the preupgrade script. > Problem 3) below explains why I can't verify if the postinstall script > has the same problem. > > 2) For Snow Leopard, I am not seeing a receipt in the /Library/Receipts > folder after the install script runs successfully. > > 3) For Snow Leopard, whether I remove old copies of our application > before installing or not, I always see the preupgrade and postupgrade > scripts run. I never see the preinstall and postinstall scripts run. > Since I can't find a receipt, I can't remove that for testing. > > Are these known problems? I am willing to enter bug reports if these are > real problems but I don't want to raise a false alarm if I'm just doing > something stupid. Is there now a "Use Receipt" flag I'm missing from > PackageMaker or something like that? > > I have attempted to look through the list archives of this group and I > find nothing about these problems other than my original request for > information about the missing script parameter. > > Thank you, > > Jim Dodd > Onset Computer Corporation > > > > > _______________________________________________ > 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/ariffel%40extensis. > com > > This email sent to ariffel(a)extensis.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: Missing install receipt and script parameter in Snow Leopard
by Glover,David 15 Oct '09

15 Oct '09

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Thread-index: AcpNpD9K6SVH4NJMRra4J0Ie8o9fVQAAM+AwAABJoZA= Thread-topic: Missing install receipt and script parameter in Snow Leopard You may also need pkgutil --pkgs / --forget. -----Original Message----- From: installer-dev-bounces+david.glover=prometheanworld.com(a)lists.apple.com [mailto:installer-dev-bounces+david.glover=prometheanworld.com@lists.app le.com] On Behalf Of Riffel, Allen Sent: 15 October 2009 15:41 To: Jim Dodd; Installer-dev(a)lists.apple.com Subject: RE: Missing install receipt and script parameter in Snow Leopard In Snow Leopard they were nice enough to move the receipts folder to: /private/var/db. Also, the receipts folder in that directory is all named with lower case characters: "receipts". Allen Riffel QA Engineer Extensis http://www.extensis.com/ phone: 503.274.2020 x116 email: ariffel(a)extensis.com Font and Creative Assets Management Software. Trusted by Millions. To learn more about Extensis Solutions, visit: http://www.extensis.com/en/solutions/index.jsp Notice: This communication may contain privileged or other confidential information. If you are not the intended recipient, or believe that you have received this communication in error, please do not print, copy, retransmit, disseminate, or otherwise use the information. Also, please indicate to the sender that you have received this email in error, and delete the copy you received. Thank you. -----Original Message----- From: installer-dev-bounces+ariffel=extensis.com(a)lists.apple.com [mailto:installer-dev-bounces+ariffel=extensis.com@lists.apple.com] On Behalf Of Jim Dodd Sent: Thursday, October 15, 2009 07:31 To: Installer-dev(a)lists.apple.com Subject: Missing install receipt and script parameter in Snow Leopard I have an installer package that runs on both Leopard and Snow Leopard successfully. There are three problems, though: 1) For Snow Leopard, I had to modify our postupgrade script to deal with a missing parameter passed to the scripts by the Installer.app. I do not know if it is the third or the fourth parameter that is missing. All I know is they have been there in all other versions of OS X and now they are not. There are four parameters passed to the preupgrade script. Problem 3) below explains why I can't verify if the postinstall script has the same problem. 2) For Snow Leopard, I am not seeing a receipt in the /Library/Receipts folder after the install script runs successfully. 3) For Snow Leopard, whether I remove old copies of our application before installing or not, I always see the preupgrade and postupgrade scripts run. I never see the preinstall and postinstall scripts run. Since I can't find a receipt, I can't remove that for testing. Are these known problems? I am willing to enter bug reports if these are real problems but I don't want to raise a false alarm if I'm just doing something stupid. Is there now a "Use Receipt" flag I'm missing from PackageMaker or something like that? I have attempted to look through the list archives of this group and I find nothing about these problems other than my original request for information about the missing script parameter. Thank you, Jim Dodd Onset Computer Corporation _______________________________________________ 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/ariffel%40extensis. com This email sent to ariffel(a)extensis.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/david.glover%40prom etheanworld.com This email sent to david.glover(a)prometheanworld.com Promethean Limited is a company registered in England and Wales with company number 1308938 and VAT number GB 572 2599 18 ______________________________________________ Promethean Ltd and or associated and or subsidiary companies : The views expressed in this communication may not necessarily be the views held by Promethean Ltd and or associated and or subsidiary companies. This e-mail is for the exclusive use of the addressee(s). Unauthorised disclosure, copying or distribution is prohibited. This e-mail message has been swept for the presence of computer viruses. Promethean Ltd and or associated and or subsidiary companies accepts no liability for any loss resulting from this email transmission. Promethean, Promethean House, Lower Philips Road, Blackburn, Lancashire, BB1 5TH, UK. Please update your records accordingly. Thank you! _______________________________________________ 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: Missing install receipt and script parameter in Snow Leopard
by Riffel, Allen 15 Oct '09

15 Oct '09

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Thread-index: AcpNpD9K6SVH4NJMRra4J0Ie8o9fVQAAM+Aw Thread-topic: Missing install receipt and script parameter in Snow Leopard In Snow Leopard they were nice enough to move the receipts folder to: /private/var/db. Also, the receipts folder in that directory is all named with lower case characters: "receipts". Allen Riffel QA Engineer Extensis http://www.extensis.com/ phone: 503.274.2020 x116 email: ariffel(a)extensis.com Font and Creative Assets Management Software. Trusted by Millions. To learn more about Extensis Solutions, visit: http://www.extensis.com/en/solutions/index.jsp Notice: This communication may contain privileged or other confidential information. If you are not the intended recipient, or believe that you have received this communication in error, please do not print, copy, retransmit, disseminate, or otherwise use the information. Also, please indicate to the sender that you have received this email in error, and delete the copy you received. Thank you. -----Original Message----- From: installer-dev-bounces+ariffel=extensis.com(a)lists.apple.com [mailto:installer-dev-bounces+ariffel=extensis.com@lists.apple.com] On Behalf Of Jim Dodd Sent: Thursday, October 15, 2009 07:31 To: Installer-dev(a)lists.apple.com Subject: Missing install receipt and script parameter in Snow Leopard I have an installer package that runs on both Leopard and Snow Leopard successfully. There are three problems, though: 1) For Snow Leopard, I had to modify our postupgrade script to deal with a missing parameter passed to the scripts by the Installer.app. I do not know if it is the third or the fourth parameter that is missing. All I know is they have been there in all other versions of OS X and now they are not. There are four parameters passed to the preupgrade script. Problem 3) below explains why I can't verify if the postinstall script has the same problem. 2) For Snow Leopard, I am not seeing a receipt in the /Library/Receipts folder after the install script runs successfully. 3) For Snow Leopard, whether I remove old copies of our application before installing or not, I always see the preupgrade and postupgrade scripts run. I never see the preinstall and postinstall scripts run. Since I can't find a receipt, I can't remove that for testing. Are these known problems? I am willing to enter bug reports if these are real problems but I don't want to raise a false alarm if I'm just doing something stupid. Is there now a "Use Receipt" flag I'm missing from PackageMaker or something like that? I have attempted to look through the list archives of this group and I find nothing about these problems other than my original request for information about the missing script parameter. Thank you, Jim Dodd Onset Computer Corporation _______________________________________________ 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/ariffel%40extensis. com This email sent to ariffel(a)extensis.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

Missing install receipt and script parameter in Snow Leopard
by Jim Dodd 15 Oct '09

15 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1255617081; bh=Oc/Gxy7xqDo9yRPsatp+8Zghg3GupSiBSuPWekHyi+M=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=nyR7eXtXOGqPGxPX9cYZxSuz/49/4yjHsbYFTq4kbNEr4UTDXI2iY/zlfW/jsbBfgxJjDBZuZpxEiQOrYiHdu7vAbUkz2bn3Nqa9W7XK878+N4f6Wq7D640pbfVAhn+1o+sgS+sNTCRb/Tatkk1spsi9ce2bKAwLMYAYpzdXvQQ= Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=rXhcn9oPYkm/fJZrSd5G67A9LuNosfDM8TrkHjDtQ0P05PY/ma5rj7uXjQNZzz/OQdNB+zw6WFK79G4bojY8dMa1odKSHVSlMVUPUERTfd0z+Fy178KWmk9sT1HnGaEh2yhE++aTxHha17B/3m4WP3xqzUUsAKwsZEXv0lVbZsQ=; I have an installer package that runs on both Leopard and Snow Leopard successfully. There are three problems, though: 1) For Snow Leopard, I had to modify our postupgrade script to deal with a missing parameter passed to the scripts by the Installer.app. I do not know if it is the third or the fourth parameter that is missing. All I know is they have been there in all other versions of OS X and now they are not. There are four parameters passed to the preupgrade script. Problem 3) below explains why I can't verify if the postinstall script has the same problem. 2) For Snow Leopard, I am not seeing a receipt in the /Library/Receipts folder after the install script runs successfully. 3) For Snow Leopard, whether I remove old copies of our application before installing or not, I always see the preupgrade and postupgrade scripts run. I never see the preinstall and postinstall scripts run. Since I can't find a receipt, I can't remove that for testing. Are these known problems? I am willing to enter bug reports if these are real problems but I don't want to raise a false alarm if I'm just doing something stupid. Is there now a "Use Receipt" flag I'm missing from PackageMaker or something like that? I have attempted to look through the list archives of this group and I find nothing about these problems other than my original request for information about the missing script parameter. Thank you, Jim Dodd Onset Computer Corporation _______________________________________________ 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: Conditionally build different versions of a package?
by marc hoffman 14 Oct '09

14 Oct '09

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Brent, marc On Oct 13, 2009, at 4:38 PM, Brent B. Bandelgar wrote: - Brent 2) Write a script that goes through the XML files and removes source targets & non-trial stuff from the generated XML, and deletes the corresponding packages if it's a trial distribution. Only two steps, but number 2 requires some work. manually coordinate them. Step 2 is complicated by the fact that PM may change the internal names of the XML files in the package if you change something. If you change things through the GUI, you need to verify the names of the files the script is processing. You also need to watch out for this if you've got your projects in a SCM system. You might make an apparently trivial change and then find out there are a number of files that need to be added and/or deleted from the SCM repository... Kevin _______________________________________________ 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/brent%40macworkshops.c… _______________________________________________ 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/mh%40elitedev.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.… thanx. i've got something working now, with basically manually maintained package-xml files and a small shell script that assembles 3 pmdoc project from them as needed, but i'll check this out for the long term! You could try out the Luggage scripts, which attempt to automate this by extending Make. http://github.com/unixorn/luggage ----- "Kevin Brock" <apple(a)kevin.com> wrote: The *simple* solution is to have two different installer projects, and This email sent to brent(a)macworkshops.com This email sent to mh(a)elitedev.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Missing Resources or everything gets installed but the application
by Greg Neagle 13 Oct '09

13 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com rm -f /path/to/some.pkg/Contents/Resources/TokenDefinitions.plist defaults delete /path/to/some.pkg/Contents/Info IFPkgPathMappings plutil -convert xml1 /path/to/some.pkg/Contents/Info.plist chmod 664 /path/to/some.pkg/Contents/Info.plist -Greg On Oct 13, 2009, at 1:09 PM, David Nock wrote: Yep, that looks like it. Should have looked at the logs more closely. "Diverting ./Blah.app to ./Desktop/untitled folder 5/Blah.app" Thanks Dave -Greg On Oct 12, 2009, at 8:01 PM, David Nock wrote: Hi, Has anyone encountered anything like this before? Using PackageMaker version 3.0.3, Mac OS X 10.5.8, Intel iMac. Cheers Dave -- ********************** David Nock Senior Developer Access-It Software Ltd ********************** This email and any attachments are confidential and intended exclusively for the person to whom the email is addressed. If you are not the intended recipient, do not read, copy, disclose or use the contents in any way. Please notify us immediately by return email and destroy the email and attachments. Access-It Software Ltd does not accept any liability for any changes made to this email or attachments after sending by Access-It Software Ltd. You must scan this email and attachments for viruses. The opinions expressed are not necessarily those of Access-It Software Ltd. _______________________________________________ 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/greg.neagle%40disneyan… -- ********************** David Nock Senior Developer Access-It Software Ltd ********************** This email and any attachments are confidential and intended exclusively for the person to whom the email is addressed. If you are not the intended recipient, do not read, copy, disclose or use the contents in any way. Please notify us immediately by return email and destroy the email and attachments. Access-It Software Ltd does not accept any liability for any changes made to this email or attachments after sending by Access-It Software Ltd. You must scan this email and attachments for viruses. The opinions expressed are not necessarily those of Access-It Software Ltd. _______________________________________________ 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/greg.neagle%40disneyan… _______________________________________________ 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 also whack the TokenDefinitions and the IFPkgPathMappings in the package output - ala: I've have now tried building the installer twice, once with IFPkgFlagRelocatable ticked and once with IFPkgFlagRelocatable unticked in the Info.plist and neither installer works. Is this the correct flag to be changing? With building the installers not using the pmproj file, I based the required Info.plist file and Description.plist file from a working installer. Greg Neagle wrote: You are almost certainly being bit by the "relocation" feature/ bug. Search this list for "relocation". I have moved my main development machine to 10.5 and I'm now fighting to get our installers to build with packagemaker and then install correctly. Fortunately we still have a 10.4 machine where everything works perfectly. The installers built on 10.4 install fine on both 10.4 and 10.5. All installers are built through a shell script and call packagemaker to build based on the packagemaker pmproj file. The problem here is that our Resources directory is not being included in the installer so the postinstall, postupgrade scripts are missing. After reading the man page I saw that you can specify the Resources dir but only if you don't use the pmproj file and specify all the paths directly. I have also tried this and the Resources are now included but then out main Application.app (bundled application) is not copied out of the installer into the correct folder. There are another 6 files in this folder and they are all copied correctly. I have opened the installer package and the Application.app is indeed present in the installer. Access-It Software Ltd accepts no liability for any loss, damage or consequence, whether caused by our own negligence or not, resulting directly or indirectly from the use of this email and attachments. This email sent to greg.neagle(a)disneyanimation.com Access-It Software Ltd accepts no liability for any loss, damage or consequence, whether caused by our own negligence or not, resulting directly or indirectly from the use of this email and attachments. This email sent to greg.neagle(a)disneyanimation.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Missing Resources or everything gets installed but the application
by David Nock 13 Oct '09

13 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.23 (Windows/20090812) Yep, that looks like it. Should have looked at the logs more closely. "Diverting ./Blah.app to ./Desktop/untitled folder 5/Blah.app" Thanks Dave -Greg On Oct 12, 2009, at 8:01 PM, David Nock wrote: Hi, Has anyone encountered anything like this before? Using PackageMaker version 3.0.3, Mac OS X 10.5.8, Intel iMac. Cheers Dave -- ********************** David Nock Senior Developer Access-It Software Ltd ********************** This email and any attachments are confidential and intended exclusively for the person to whom the email is addressed. If you are not the intended recipient, do not read, copy, disclose or use the contents in any way. Please notify us immediately by return email and destroy the email and attachments. Access-It Software Ltd does not accept any liability for any changes made to this email or attachments after sending by Access-It Software Ltd. You must scan this email and attachments for viruses. The opinions expressed are not necessarily those of Access-It Software Ltd. -- ********************** David Nock Senior Developer Access-It Software Ltd ********************** This email and any attachments are confidential and intended exclusively for the person to whom the email is addressed. If you are not the intended recipient, do not read, copy, disclose or use the contents in any way. Please notify us immediately by return email and destroy the email and attachments. Access-It Software Ltd does not accept any liability for any changes made to this email or attachments after sending by Access-It Software Ltd. You must scan this email and attachments for viruses. The opinions expressed are not necessarily those of Access-It Software Ltd. _______________________________________________ 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've have now tried building the installer twice, once with IFPkgFlagRelocatable ticked and once with IFPkgFlagRelocatable unticked in the Info.plist and neither installer works. Is this the correct flag to be changing? With building the installers not using the pmproj file, I based the required Info.plist file and Description.plist file from a working installer. Greg Neagle wrote: You are almost certainly being bit by the "relocation" feature/bug. Search this list for "relocation". I have moved my main development machine to 10.5 and I'm now fighting to get our installers to build with packagemaker and then install correctly. Fortunately we still have a 10.4 machine where everything works perfectly. The installers built on 10.4 install fine on both 10.4 and 10.5. All installers are built through a shell script and call packagemaker to build based on the packagemaker pmproj file. The problem here is that our Resources directory is not being included in the installer so the postinstall, postupgrade scripts are missing. After reading the man page I saw that you can specify the Resources dir but only if you don't use the pmproj file and specify all the paths directly. I have also tried this and the Resources are now included but then out main Application.app (bundled application) is not copied out of the installer into the correct folder. There are another 6 files in this folder and they are all copied correctly. I have opened the installer package and the Application.app is indeed present in the installer. Access-It Software Ltd accepts no liability for any loss, damage or consequence, whether caused by our own negligence or not, resulting directly or indirectly from the use of this email and attachments. _______________________________________________ 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/greg.neagle%40disneyan… This email sent to greg.neagle(a)disneyanimation.com Access-It Software Ltd accepts no liability for any loss, damage or consequence, whether caused by our own negligence or not, resulting directly or indirectly from the use of this email and attachments. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Fed up with PackageMaker, any advice?
by Kevin Brock 13 Oct '09

13 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Oct 13, 2009, at 8:12 AM, Sidney San Martín wrote: Thanks, Kevin. I'm not seeing this option in the PackageMaker UI, and if I create a component but leave its contents empty, PackageMaker spits out a warning and doesn't include it in the built package. Am I missing something? Kevin _______________________________________________ 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.… On Fri, Oct 9, 2009 at 12:35 PM, Kevin Brock <apple(a)kevin.com> wrote: It's possible to create a script-only target. Put one as the first component, and one as the last. It's a hack, and you'll see that target in the GUI when the scripts are run, but it works. I really wish they'd either kept the global pre- and post- or let us define our own actions to extend what's possible in the actions pane. It's not an explicit option. You can create an empty folder, add the folder as a component, but mark the folder as not to be installed. You can add scripts to the component which will be run, even though nothing from the component is getting put on the disk. Another approach is to make sure that your first and last components are things which will always be installed, and put your pre-install script as the pre-install for the first component, and your post- install as the post-install for the last component. It's a hack, but so are script-only targets. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Fed up with PackageMaker, any advice?
by Sidney San Martín 13 Oct '09

13 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Fri, Oct 9, 2009 at 7:22 PM, Iceberg-Dev <dev.iceberg(a)gmail.com> wrote: > > Apple does not follow this recommendation so just don't follow it if you > don't want to. Just don't overwrite permissions and you will be fine. > > Yet, considering 4., I would recommend using 2 packages. one for the common > components and another for the ones that need to be install only when > specific requirements are met. OK. Not splitting the package up into a component for each system directory makes it much simpler. I'm trying to decide whether to just install the agent's launchd.plist to a temporary location and handle it in a postflight script (simpler) or split up common, 10.4-specific and 10.5+ behaviors into separate sub-packages as you recommend and turn the top-level package into a metapackage. That would take OS detection out of the scripts, but I'd have to carefully plan which actions go in which of the three postflights. > If the OS target is 10.5, postinstall and preinstall are the same as > postflight and preflight. OK... it does look like the other options disappeared when PackageMaker switched to targeting 10.5. They're back after switching back to 10.4. In a 10.4-targeted package, does 10.5 still treat *install the same as *flight? By the way, I was about to ask if Iceberg could be scripted, but found freeze. Great! Unfortunately, when I run freeze on my current project, it spits out "freeze: Build failed / Insufficient privileges set". I have no problem building from the GUI. Any idea what's going on here? _______________________________________________ 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: Fed up with PackageMaker, any advice?
by Sidney San Martín 13 Oct '09

13 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Fri, Oct 9, 2009 at 12:35 PM, Kevin Brock <apple(a)kevin.com> wrote: > It's possible to create a script-only target. Put one as the first > component, and one as the last. It's a hack, and you'll see that target in > the GUI when the scripts are run, but it works. I really wish they'd either > kept the global pre- and post- or let us define our own actions to extend > what's possible in the actions pane. Thanks, Kevin. I'm not seeing this option in the PackageMaker UI, and if I create a component but leave its contents empty, PackageMaker spits out a warning and doesn't include it in the built package. Am I missing something? > Can't say much about raw editing mode. Haven't used that much. Since I > only need to install on 10.5+ for most of my packages I've been using flat > packages, and they're structured very differently from bundle packages. > They also don't support plugins, so they wouldn't work for you... > I've been pretty happy with the XML files, because they make it easy to > write build scripts that manipulate the PM generated files after the fact to > make needed changes. For example, there's a bug WRT versions that you need > to work around by modifying the files by hand if you're doing automated > command line builds. It only affects bundles that are being installed, so > it doesn't sound like you need to worry about it... It looks like I can include everything (except the plugin) with the scripts directory path, so I may be able to avoid the problems with raw editing. If I can get a good, working pmdoc put together in PackageMaker, modifying it at build-time probably works. > From your description it sounds like what you need is possible under PM > without much customization beyond the plugin you already have. Your level > of comfort with the XML files is an important factor if you need to tweak > things after the fact though. > There are a number of people on this list using Iceberg, a freeware > installation package builder, but I don't know much about it myself. It's > at > http://s.sudre.free.fr/Software/Iceberg.html > if you want to take a look. I tried Iceberg... I like it a lot, it's much more straightforward than PM and let me put together a working package in no time. Even if, for whatever reason, I go back to PackageMaker (I can't find a way to script Iceberg, for instance), using Iceberg let me get unstuck making a package so I move on to finishing my scripts and plugin. Thanks again. _______________________________________________ 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