Re: PackageMaker allow for optional install?
Re: PackageMaker allow for optional install?
- Subject: Re: PackageMaker allow for optional install?
- From: Bill Coderre <email@hidden>
- Date: Tue, 06 Oct 2009 16:30:23 -0700
On Oct 6, 2009, at 3:39 PM, Brant Sears wrote:
> I know how to do that - but I didn't know you could do it for things that weren't part of your package.
>
> This point is critical: At the time I make this installer I won't know what the custom install items are. I'm discovering these on the CD at the time the installer runs.
Tweaking a running installer is completely unsupported.
You might be able to create a small program that scans the CD for packages, and creates an installer package on the fly, then opens the package with Installer.app. Apple has no such functionality to accomplish this, so you're on your own.
This is not a trivial program to write, but could be done in under a week.
Note that if you scan and create a "distribution" file, it could easily end up installing stuff that you should not install. For apps this might not be a big deal, but if you install an old kext on a new OS, it could cause crashes, so think carefully about what you are doing.
So you probably should not create disks that include installers that install any extensions.
If you scan and create a "bundle" installer, there would be a bunch of different issues to work out -- each individual package might be able to veto the installation of the entire collection.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden