With the understanding that I will eventually be using something more sophisticated to deploy postboot packages, what’s the best way to create a package of a package for the purposes of simply dropping that package into a location on my target drive?
Is it as simple as creating a new project and dragging the pkg in?
I need to be able to call the package later on in the install process via a 2nd boot script.
But to answer the question, I’d say that is an OK way to do it, but definitely not a good way to do it. If any of the permissions get screwed up it could get awful hairy, awful fast.
Nate
P.S. I couldn’t resist – Yo dawg, I heard you liked packages, so we put a package in your package so you can install while you install. (See[url] http://knowyourmeme.com/memes/xzibit-yo-dawg%5B/url%5D for explanation).
We’re looking into DeployStudio, or JAMF, but right now it’s a good ‘ole firewire drive.
Understood on the permissions warning. In this case, it’s a command line install that lives on a disk image that will be plopped down on disk via a package. Not the most elegant thing in the world. 😉
Comments are closed