Re: Can a metapackage display the licenses for the component packages?
Re: Can a metapackage display the licenses for the component packages?
- Subject: Re: Can a metapackage display the licenses for the component packages?
- From: Stéphane Sudre <email@hidden>
- Date: Thu, 7 Sep 2006 22:46:40 +0200
On jeudi, septembre 7, 2006, at 08:38 PM, Dave Camp wrote:
I'm creating a metapackage that will install my software, and some
necessary 3rd party software that comes in it's own package. What I
would like to do is have the metapackage display the licenses and
read-me's for both component packages before the install.
Is that possible? Or do I have to create a single (combined) license
and read-me for the metapackage myself?
o It is not possible through the standard way as Luke wrote.
o It could be done without combining licenses (which may be a problem):
* If you require Mac OS X 10.4 or later, you could write an Installer
Plug-in to display the licenses and let the user validate them. If you
want the UI of that plug-in to look like the Installer License UI,
there's some code available under the BSD license to do that.
* if you need to be 10.3 or earlier compatible, you can:
* Remove the license step from the metapackage
* Code a helper tool which will display the licenses and let the user
accept or refuse them.
* Call this tool from the preflight script of the metapackage.
Of course, you could add this tool to all the packages and their
preflight script so that you don't have to rewrite the helper tool if
you add or remove package from the metapackage.
_______________________________________________
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