October 2009 - Installer-dev

Re: Conditionally build different versions of a package?
by Brent B. Bandelgar 13 Oct '09

13 Oct '09

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com You could try out the Luggage scripts, which attempt to automate this by extending Make. http://github.com/unixorn/luggage - Brent ----- "Kevin Brock" <apple(a)kevin.com> wrote: > > 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. > > > > The *simple* solution is to have two different installer projects, and > > 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… > > > > This email sent to brent(a)macworkshops.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 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 -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… _______________________________________________ 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.… 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 This email sent to site_archiver(a)lists.apple.com

1 0

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) 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/site_archiver%40lists.… 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 site_archiver(a)lists.apple.com

1 0

Re: Conditionally build different versions of a package?
by marc hoffman 13 Oct '09

13 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Kevin, thanx! marc _______________________________________________ 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 may have made the renaming sound worse than it is... Generally it's only an issue when you add or remove something. yeah, but i've seen it happen often enough even in the little time/ scope i've been using PackageMaker for. a simple change, and at best you see all files modified in SVN, often times, half show as removed and new (ie they switched around names/order. :( You could probably write the scripts so that they figure out which XML file is which component based on the contents, instead of hard- coding the file names. that's probably what i'll do long term, with just a separate 2nd installer for the immediate release. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Conditionally build different versions of a package?
by Kevin Brock 12 Oct '09

12 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812) Kevin, 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.… marc hoffman wrote: 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... thanx. so the real answer is that i wasn't missing anything, and there's no official way to do it, besides manually messing with the raw files - i was afraid of that. guess for the short term i'll try to go with two separate projects, then :(. it's a shame, really. if only the random renaming/reordering of the files wouldn't happen, this would he halfway feasible (ie, keeping the folder in almost-sync thru, say, Araxis Merge)... I may have made the renaming sound worse than it is... Generally it's only an issue when you add or remove something. You could probably write the scripts so that they figure out which XML file is which component based on the contents, instead of hard-coding the file names. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Conditionally build different versions of a package?
by marc hoffman 12 Oct '09

12 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Kevin, It's accurate though... One approach might be Only two steps, but number 2 requires some work. thanx, marc _______________________________________________ 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.… that's a very helpful anser ;) 1) Build a package that has everything 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. The *simple* solution is to have two different installer projects, and 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... thanx. so the real answer is that i wasn't missing anything, and there's no official way to do it, besides manually messing with the raw files - i was afraid of that. guess for the short term i'll try to go with two separate projects, then :(. it's a shame, really. if only the random renaming/reordering of the files wouldn't happen, this would he halfway feasible (ie, keeping the folder in almost-sync thru, say, Araxis Merge)... This email sent to site_archiver(a)lists.apple.com

1 0

Re: Conditionally build different versions of a package?
by Kevin Brock 12 Oct '09

12 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812) It's accurate though... One approach might be Only two steps, but number 2 requires some work. 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.… marc hoffman wrote: is this possible? Probably but it would be more complex. that's a very helpful anser ;) 1) Build a package that has everything 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. The *simple* solution is to have two different installer projects, and 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... This email sent to site_archiver(a)lists.apple.com

1 0

Re: Conditionally build different versions of a package?
by marc hoffman 12 Oct '09

12 Oct '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com that's a very helpful anser ;) _______________________________________________ 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.… is this possible? Probably but it would be more complex. This email sent to site_archiver(a)lists.apple.com

1 0

Re: metapackage component conditionally set required
by Iceberg-Dev 09 Oct '09

09 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=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=OlORQ4nZKODVTU91yTF+BltnivCgHh4JfDMgQgGTWUQ=; b=Vk+e/huRlyCj5YovvcS2IcQlqtwOEHeJfHNtlhzPogCzDBS7ap56+p0jFxZst/pykh V0xhoHs4J81cku5SnHKtiMS//42T+00SyQd8gxKClu9cRQNpR/Ga2+E5E7v54m84Zn9K k2FFLPJrR2bh0pEzaTodh6yWL0TJdWjWpItf4= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=kXfSyGWPJVJ9WJe9mw1z6cxldFh/lASnPy+MCIQb7MnOpGgIR/vaoJVmDLWSLhZTgb 3aZXPbQnPCNHxp1+Mlyb/VTlg/6Uf9z0Hfv6JdKrjVRrARbtUWN7BV4Ppx3lBaQfIoXU G4UOoI5ObkwCLd0FfUoRLBXqq+TavTtIHjh0o= On Oct 9, 2009, at 6:43 PM, Andy Mroczkowski wrote: Hi all, I have a metapackage that has two sub-components. These components install resources for a particular architecture (Intel or PPC). I can conditionally select or de-select the sub-components with requirements scripts, but I'd like to automatically make the appropriate component Required and disable the other component. For example, if I'm installing on an Intel macine, the Intel sub-component would be Required, while the PPC component would be disabled. Yes it can. Here is something to get you started. function installer_choice_1_selected(isStart) { var tSelected; tSelected=!choices.installer_choice_2.selected; if (isStart==true) { return tSelected; } return (tSelected && my.choice.selected); } function installer_choice_2_requirement() { var tResult; tResult=myfunctiontocheckifthearchitectureisenabled; return tResult; } _______________________________________________ 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.… Can this be accomplished? You just need to have one component check if it needs to be required or disabled and then you make the second component state depend on the first one. <choice id="installer_choice_1" start_enabled="false" start_selected="installer_choice_1_selected(true)" selected="installer_choice_1_selected(false)" title="Intel" description="One Moore thing..."> <pkg-ref id="com.intel.blahblah"/> </choice> <choice id="installer_choice_2" start_enabled="false" start_selected="installer_choice_2_requirement()" title="PowerPC" description="Use at your own RISC"> <pkg-ref id="com.powerpc.blahblah"/> </choice> This email sent to site_archiver(a)lists.apple.com

1 0

Re: Conditionally build different versions of a package?
by Iceberg-Dev 09 Oct '09

09 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=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=af4J2bRT9LpnSWelrYu70O7WkpurtV5zUjav1ne/0RE=; b=fTGI9kUNcdbPf1BHpnGXACDVubuDLWFIg4KSB8QVdP7iZRUOMTWKk8XbkmKOYxrriD gDxXj6X+jBH+Ifzn9OOKe1pUOgc5zI33r6sjJaR5VdX6N2d2gVGydBFW5xQvSoyxAwtJ MZXuAifKURKXTi8GT3ihNH2miiGqW1hbcXV3U= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=CamHwSwduaX5ifdZWqmw8EDn6QmkWZh4Ppx59wg369J6G8v+J/KtpDOxiElXjs1TZp CAUOF5t3ybUXupH2yYdGsB+CuGh40L2af/LwCDRhd1OEa2wZO9rJRTNKfeU87MgNvBQQ OTzFIZor7u/doau/qIFQkgsM7ZkxYw+EFrMX0= On Oct 9, 2009, at 2:21 PM, marc hoffman wrote: Hi. Probably but it would be more complex. _______________________________________________ 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 been staring at this problem for a while now and don't see an obvious solution, i'm hoping that someone can help out. as part of my (automated/scripted) build process, i would like to build two versions of my installer package, each of which would conditionally exclude/include a certain subset of components. more specifically, i'm installing a framework product, and would like to (obviously) exclude the source code and release level binaries from the trial version, and instead ship a differently-compiled trial binary of the framework. as my installer is deploying quite a few items that will be shared between trial and non-trial versions, i'd really love to avoid aintaining two separate copies of the .pmdoc, and be able to build both versions of the installer from one set of files. is this possible? This email sent to site_archiver(a)lists.apple.com

1 0