Old workaround was breaking package files in my build train.

[jeffbearer]

Wanted to drop a note, to hopefully help others save some time. and report some errors to the dev team.

I spent a couple of days messing around trying to figure out why my build train was not including any pkg files any longer. In the older revisions of instadmg I’m pretty sure I had to put a nearly empty InstallerChoices.xml in the directory instadmg/InstallerFiles/InstaUp2DatePackages in order to get packages to install.

Now against r300 this was causing my build to complete without error or telltale debug messages of the problem, but it wasn’t installing any of the pkg files I wanted to include. Turns out the problem is that instadmg.bash looks on or around line 994 to see if :

[code] [ -e “`dirname “$INSTALL_ITEM”`/InstallerChoices.xml” ][/code]

Then on or around line 1046 it tries to use an installerChoices.xml that is inside the package because the previous had test succeeded:

[code]/usr/sbin/installer -verboseR -dumplog -applyChoiceChangesXML “$TARGET/InstallerChoices.xml” [/code]

The problem is that the test does not check the existence of the same file this command uses.

Also curiously the 2>&1 to log for the installer command does not record the error about the missing InstallerChoices that you get when you run the same command by hand.

I deleted my dummy InstallerChoices.xml and It looks like this build is going to succeed and install the package files, the debug log showed a lot more activity on the pkg install than before that was little more than the start and finish message.

[larkost]

I just put in what I think might be a fix (I don’t have this in a test rig yet). Try rev302 and see if it is fixed for you. Thanks for the report.

[jeffbearer]

Gotcha, The question I have is that the installer command that you fixed to point to the generic InstallerChoices.xml to be used by all packages.

[code]instadmg/InstallerFiles/InstaUp2DatePackages/InstallerChoices.xml[/code]

is the same functionality that instadmg used to have. In looking at the code I thought that perhaps the functionality was upgraded and looking inside the package directory for the InstallerChoices.xml was a new valid operation.

[code]instadmg/InstallerFiles/InstaUp2DatePackages/clearReg.pkg/InstallerChoices.xml[/code]

But after looking at r302 I guess that was just a mistake? Maybe what is the new code is the section above that does not require the InstallerChoices.xml at all. Thanks for the help.

[Author]

Posts