Re: multiple license and readme files
Re: multiple license and readme files
- Subject: Re: multiple license and readme files
- From: Stéphane Sudre <email@hidden>
- Date: Mon, 22 Jan 2007 09:02:32 +0100
On dimanche, janvier 21, 2007, at 03:31 PM, Dan Nigrin wrote:
Aggregate the ReadMe and License files into one ReadMe and one
License file and put them in the root metapackage?
This is somehow how Safari is doing for the acknowledgements.
Since you need to run on 10.3, an Installer Plugin would not do any
good.
Stéphane, thanks for the response - although this is a straightforward
option, the reason I want to do it the way I originally described is
because one of the packages is from a different software provider.
They have given me the permission to bundle their installer within
mine, but I would much prefer not to "mess" at all with their
installer, in order to keep the separation of "their" stuff from "my
stuff" fairly clean...
While this solution would not require changing the installers (since
the License and ReadMe are just not displayed), another solution could
be:
o Writing a small tool called by InstallationCheck that would display
the different ReadMe and License documents in a series of pane. The
issue with this is that it may be tough to make it work when installing
with ARD (no UI).
In the interim, I did find a previous post on the list covering some
of the same ground:
http://lists.apple.com/archives/installer-dev/2006/Jan/msg00058.html
I'm interested in further exploring the bit that says "I suppose it's
also possible to chain several installers together, such that when the
user finishes one installer, the next is automatically launched."
Could anyone suggest an approach to how I could do this, with the
following constraints:
* Only one installer package visible to end user
* Run a postflight script after both pacakges installed, but which is
currently NOT part of the second package (and which is the other
software provider's, so I would like to not add anything to their
package).
This would probably require killing Installer.app in the postflight
script since chained packages installation is available only from 10.4
IIRC.
Another issue with this could be permissions. If the first package
requires Root/Admin authentication, the postflight script is run as
root so Installer.app might be run as root when launched from this
script.
Another suggestion could be to just use the installer command line tool
and build the UI around it for the license and readme documents.
_______________________________________________
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