site_archiver@lists.apple.com Delivered-To: Installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Cl/SpFm7EDHYTZjkX0ltFS1uqJBvAqHaVmHAOBe7ZX4=; b=stpyL9smsVVP8hS2LGgnNzuRCxafXETvLl5MrKRui7FB9WnRrtuH+7mjvaIIdX+Av3 H+dH5Z4/eBagW4UDIAMD9ZH3xOVYEwcnKRxzOL+zasFibSVfE0sMVYksT3OzNEN3QAo1 GVw/1C2UEiUqAmOM04b4nzFwSx46NMfgzG/xA= On Thu, Jun 30, 2011 at 4:18 PM, Karthikeyan M <karthikeyan.mac@gmail.com> wrote:

Hi,

We have few packages(.pkg) created using Composer. Composer does not provide GUI options to add Installation requirements, it requires scripting to add in Package. We may need to add one or two Installtion requirements. I noticed PackageMaker has a option to choose the requirements from the list. I opened the package in PackageMaker to add the Installation requirements.  When I add any installation requirements the packages becomes .mpkg. Is this the normal behaviour? Because we need packages to be in .pkg.

Assuming you are referring to a package with Mac OS X v10.5 as the target. Requirements are JavaScript scripts attached to choices. A choice is defined in a distribution script. A distribution script is in a distribution. The extension for distributions is .mpkg.

Also, it does not provide a list to choose the processor type(Intel, PPC). Any suggestion for this?

Use the "Result of JavaScript" item and write your own script (and be amazed by the size of the text editor view). or Use another solution. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com