Installer project directory clarifications
Installer project directory clarifications
- Subject: Installer project directory clarifications
- From: Mike <email@hidden>
- Date: Sun, 25 Mar 2007 09:20:52 -0700
I want to make a single-package installer that contains all my product's
files but I also want to be able to have that package be deliverable in
a Managed Install via Apple Remote Desktop 3.
The Software Delivery Guide is a little unclear as to exactly which
installer packages can and cannot be delivered via this method.
In the fourth chapter it says "Packages contain a product or a product
components", but then later on page 31 the directory hierarchy appears
to require a separate "component" directory for each component in the
install. What if I only want one package but multiple component
directories in that package?
So my two questions are:
1) What is the proper directory hierarchy for a single project directory
full of a variety of product files for a single package and
2) is the directory hierarchy listed on page 31 mandatory - that is,
does the installer actually read the directory hierarchy and then
execute the other items such as "extras" at runtime?
Thanks,
Mike
_______________________________________________
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