Installer Choices for OS installation

[Theilgaard]

In my catalog file, I have added this line (as described in the catalog template file) in the Settings section in the top of the file:
Installer Choices File: InstallerChoices_Customer.xml sha1:3c4198149b9c3308360bdb8476a348abadc204b4

This file is laying beside my Mac OS 10.6 dmg file.

I run InstaUp2Date, like this (I am standing in /):
[code]$ sudo ./instadmg_run/AddOns/InstaUp2Date/instaUp2Date.py Customer

Parsing the catalog files for Customer
Installer Choices File: InstallerChoices_Customer.xml – looking based on guessed name and verified in less than one secondTraceback (most recent call last):
File “./instadmg_run/AddOns/InstaUp2Date/instaUp2Date.py”, line 716, in
main()
File “./instadmg_run/AddOns/InstaUp2Date/instaUp2Date.py”, line 662, in main
thisController.parseCatalogFile()
File “./instadmg_run/AddOns/InstaUp2Date/instaUp2Date.py”, line 266, in parseCatalogFile
raise commonExceptions.InstallerChoicesFileException(‘Unable to find %s: %s (checksum: %s)’ % (settingLineMatch.group(“variableName”),
settingLineMatch.group(“variableValue”), settingLineMatch.group(“fileChecksum”)), choicesFile=fileLocation, lineNumber=lineNumber)
Resources.commonExceptions.InstallerChoicesFileException:
Unable to find Installer Choices File: InstallerChoices_Customer.xml (checksum: sha1:3c4198149b9c3308360bdb8476a348abadc204b4)
[/code]
Is this a bug, or did I misplace the InstallerChoices file?
If I comment out the “Installer Choices File” from the catalog file it runs as it should (also with my own custom changed instadmg.bash-script which loads installer choices files according to the name in “Output Volume Name”).

[Allister Banks]

Hey Theilgaard,

Please use the path to the installerchoices.xml file with the filename and let us know if that works(it should). Thanks,

Allister

[Theilgaard]

I changed the path to this:
../../InstallerFiles/BaseOS/InstallerChoices_Customer.xml

And now it has found it.

I think InstaUp2Date should be able to find this folder by itself. 😉

Thanks.
Søren

[tristan_mason]

slightly different output: “permission denied” when i try to run it in the terminal…

[dead2sin]

Are you running it as sudo?

Nate

[tristan_mason]

Hi Nate

I am indeed. Somewhere in the scheme of things I missed this whole step when I started this whole instaDMG thing so i’m coming at this having done most everything else. DERP! Anyhow do I just put the xml file in the folder and run the workflow as normal or do I have to run the xml from the terminal and then run the workflow?

Cheers

Tristan

[dead2sin]

[QUOTE][u]Quote by: tristan_mason[/u][p]Hi Nate

I am indeed. Somewhere in the scheme of things I missed this whole step when I started this whole instaDMG thing so i’m coming at this having done most everything else. DERP! Anyhow do I just put the xml file in the folder and run the workflow as normal or do I have to run the xml from the terminal and then run the workflow?

Cheers

Tristan[/p][/QUOTE]

What you do for installerchoices is place it in any folder within InstallerFiles and then run ./checksum.py on it. It’ll spit out the full path to the InstallerChoices file as well as a checksum. You include this on the vanilla catalog using this format:

[code]Installer Choices File: tab [/code]

Note its only the full path to XML + Checksum, rather then description, path and checksum.

Then, once you run your instaup2date build, it’ll use this installer choices.

Nate

[tristan_mason]

thanks, that’s crystal clear. does it matter where it goes in the catalog file? under the includes perhaps?

regards

tristan

[tristan_mason]

got it working. just popped it under my includes and it’s going like a treat. Now I have it working i shall go back and look at any mpkg’s i’m using and apply this practice to anything that needs it. a great addition to the tools.

tristan

[Author]

Posts