Re: Required Packages in Metapackage (Metapackage not required)
Re: Required Packages in Metapackage (Metapackage not required)
- Subject: Re: Required Packages in Metapackage (Metapackage not required)
- From: email@hidden
- Date: Wed, 30 Nov 2005 08:46:04 -0500
On 29/11/2005, at 7:07 AM, email@hidden
wrote:
> I am creating a CUPS printer driver and need to put the driver in
/
> Library/Printers/Kodak/... and its PPD file in /Library/Printers/
> PPDs/Contents/Resources/en.lproj. While I currently move everything
> to the Kodak folder and then run a postflight script to copy the
> PPD file where it belongs, this seems like a good place to use a
> metapackage file (10.3.9 or later, so dist files need not apply).
I
> can create the two .pkg files, and I can create a metapackage file
> that includes the two .pkg files (both with the Required
> attribute), but the .mpkg file allows the user to deselect either
> (or both) packages after clicking the Customize button during
> installation. While I don't mind them seeing there are two
> packages, I need both be installed for the driver to work.
and the answer is...
My supervisor pointed out that I can
use /Library as my root instead of /Library/Printers, then create a Printers
folder with Kodak and PPDs subfolders and put the files and folders I want
to install inside them. Naturally, I don't overwrite existing folders,
and I use a script file to set the owner, group, and permissions properly
for the "installed" Printers folder and items inside it. (Even
better, this approach can be used for widely separated items, such as a
printer driver and a utility or application. It sure seems obvious once
someone points it out!) _______________________________________________
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