Re: Required Packages in Metapackage
Re: Required Packages in Metapackage
- Subject: Re: Required Packages in Metapackage
- From: "Perbix, Michael" <email@hidden>
- Date: Mon, 28 Nov 2005 15:47:31 -0500
- Thread-topic: Required Packages in Metapackage
Title: Re: Required Packages in Metapackage
Yup,. I am guessing you can do that. But as easy as IceBerg makes it, you don’t have to mess with all that. Unless your client installing your package has some funny permissions done on purpose. Of course, if they repair permissions at any time they will have the same result, but at least it wont be YOUR fault 8-)....
-Mike
On 11/28/05 3:44 PM, "Tobias Peciva" <email@hidden> wrote:
How about fixing up the privileges in the postinstall script? We use
chmod/chown in our postinstall scripts to guarantee that all
installed components have the correct ownerships and permissions.
Cheers,
Tobias
On 29/11/2005, at 9:40 AM, Perbix, Michael wrote:
> Except there is some known problems with doing this and using ROOT
> authentication where the priv's of the directory paths to your
> items being
> installed get messed up.
>
> I have come across this many times....the recommended way to to do as
> suggested and create a separate package for each set of items that
> need to
> be installed at a given location, and make sure the root is set
> that folder,
> then combine them into a Meta-Package.
>
> At least, that is why my research and info from Apple Support has
> come up
> with.
>
> -Mike
>
>
> On 11/28/05 3:21 PM, "Tobias Peciva" <email@hidden> wrote:
>
>> 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.
>>
>> In the Info.plist for each .pkg file, make sure you have:
>>
>> <key>IFPkgFlagIsRequired</key>
>> <true/>
>>
>> If this is set, the user will not be able to uncheck your packages.
>> The only exception is if a package has already been installed on the
>> target machine, in which case it can be unchecked. But of course if
>> the package is already installed, this doesn't actually matter: The
>> installer would skip it anyway.
>>
>> Note that you could also place all files in the same .pkg file
>> (no .mpkg required), set the default location to "/", the relocatable
>> flag to "false" and just make sure that your package root matches the
>> directory structure you want on disk. If you don't specifically need
>> the user to be able to select which packages to install, this is
>> probably preferable.
>>
>> Cheers,
>> Tobias Peciva
>> Pharos Systems
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Installer-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>> 40lmsd.org
>>
>> This email sent to email@hidden
>
> _______________________________________________
> Michael Perbix
> Lower Merion School District
> Telecommunications Specialist
> (610) 645-1964 - Work
> (610) 896-2019 - Fax
>
>
_______________________________________________
Michael Perbix
Lower Merion School District
Telecommunications Specialist
(610) 645-1964 - Work
(610) 896-2019 - Fax
_______________________________________________
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