July 2011 - Installer-dev - lists.apple.com

Requirement for amount of free space on root volume in installer?
by Mac QA 08 Jul '11

08 Jul '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=1HhKDcG5uUQ3fjbrZewFY9oLAunK2OwWrP5qhtsGWXc=; b=bZX6McyeU4BWSlaKwgukpl0YDZPgOr2YDQuoIYwi4NOHDLJaanpyXMiay5KXyzeeVa r3KJ8vXPVRyeq6ePhNcaVBQZzxo8bDwlcHClkOgYZrnU2sK7Y3NFX13feJCHD4ESH1vW cyBV5iC3xaSnqgQFztqCRsmSE8DNvVfTuaSPw= Hi, I have an installer pkg created from an Iceberg packproj -- it is a normal package (when you right-click it says "show package contents"). I want to add a requirement that there be at least a gigabyte of free space on the root volume. The requirement editor in Iceberg doesn't seem to have a way to support this. Only gestalt, sysctl, etc, which don't seem to provide a way to do this check. Please correct me if I am wrong. So then I saw that the requirements editor in Package Maker 3 does have a way to specify "Megabytes available on target" so I created a simple test package using Package Maker and set this requirement. My intent was to then examine the pkg it creates and try to copy that into my Iceberg produced pkg manually. However, the pkg that Package Maker produced didn't even have a "show package contents" when right-clicked, so there was seemingly no way to inspect it. Can anyone suggest the proper way to perform this check using Iceberg? Thanks MacQAGuy _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Add Installation Requirements to the existing .pkg
by Stephane Sudre 08 Jul '11

08 Jul '11

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)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 :content-type:content-transfer-encoding; bh=Urt/jgEqp/lhPc5w2o7FtEdTRwV4rCwM8cCsAJCrKAA=; b=fMvppsV4KsfcMhbcR3KJ8WWnUYWWmR1Te2KeIVINFmpSMEa4HGPHebOrJGJ+mB9R9V Xp/20JrLCp7/cAVuim4fyHF0fFKoPrP2Cv8Pu/+y3jYgnx/vyS5nwZ1zZpsTSx8z85r6 8y6sjSYUYg9wC9sCpIR3haC2bqrIJKQpewCUw= When you need to find the value for a sysctl, the easy solution is to use the Terminal application: 1. Open Terminal. 2. Type: sysctl -a Another solution includes using Google: http://forums.macrumors.com/showthread.php?t=608084 And finally, it's sometimes worth searching the archive of this mailing-list (lists.apple.com: http://lists.apple.com/archives/installer-dev/2010/Feb/msg00090.html My $0.02 On Thu, Jul 7, 2011 at 7:34 PM, Karthikeyan M <karthikeyan.mac(a)gmail.com> wrote: > Hi, > > In Packagemaker I noticed there is a option to set the Installation > Requirements as a result of "Sysctl". The manual page show the list of > sysctl values like hw.cputype, but does not the value for the Intel > processor. > What is the value for Intel processor of sysctl hw.type command? > > Also, Could someone help me in providing the Sysctl command values? > > Thanks & Regards, > Karthikeyan > > > On 30/06/11 10:03 PM, Stephane Sudre wrote: >> >> On Thu, Jun 30, 2011 at 4:18 PM, Karthikeyan M >> <karthikeyan.mac(a)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(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/installer-dev/dev.iceberg%40gmail.com > > This email sent to dev.iceberg(a)gmail.com > _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Add Installation Requirements to the existing .pkg
by Karthikeyan M 07 Jul '11

07 Jul '11

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=cOOxYNF1pREQQCDIUV2Sg21dzeJIt1WzaTjzhUOH2UI=; b=tFkCPsa3kXEzbiBY+l8JQofaRicygb259rQGdebpQejpEN2xGwQqVSsq7UamsDU9r/ bh8Ugr1P6cS18iF6dGl5PSox3FgAhyYED6M6k18WAZxewMpb17ONav4pEwWb9YkckDHm D+WCxGyOpVo0ycUiG1dfGTjYPJRHHcjxs79to= User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0 Hi, Also, Could someone help me in providing the Sysctl command values? Thanks & Regards, Karthikeyan On Thu, Jun 30, 2011 at 4:18 PM, Karthikeyan M <karthikeyan.mac(a)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 _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… In Packagemaker I noticed there is a option to set the Installation Requirements as a result of "Sysctl". The manual page show the list of sysctl values like hw.cputype, but does not the value for the Intel processor. What is the value for Intel processor of sysctl hw.type command? On 30/06/11 10:03 PM, Stephane Sudre wrote: Use another solution. This email sent to site_archiver(a)lists.apple.com

1 0

Re: handling configuration files
by Iceberg-Dev 06 Jul '11

06 Jul '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; bh=NkUNtx67QGliaR25PiBr4rHTb2xnZQekcEhpcwxkg7Y=; b=du220eqYYR0zn8/q4SlyMdnx9fKRvC61lPAAafyNYgZIyoYHzh4sVsMSIeCsBbd7s7 D3oSO08aQy6pZ4gWJkRLHC/fGnZZlpadSto4w9D3osUcpiQBOTFKBF76a+dXlWfLyJDB dPx1h9jXhcHhzpTfxPWmiEInaIgjepumClQv4= On Jul 6, 2011, at 2:17 AM, Joe Damato wrote: Hi - The application I'm trying to package comes with a set of default configuration files and plists, however, these files are modified after installation via postinstall so that they suit the user's system (for example, picking a network interface or how much RAM to use for a specific data structure, etc). When the user installs a new version of the packaged application, these configuration files are overwritten. I tried using requirements to test for the existence of the config files and if they exist, skip installing one of the contents that contains the config files, but I was unable to get this to work properly. Doesn't seem like requirements were intended to be used like that. What does you requirement look like? Any hints for dealing with config files? I've seen package management systems in other environments that allow you to mark a packaged file as a config file so that it is not overwritten on upgrade. Maybe something like that is possible with package maker and I'm missing it? _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Requirements should word to accomplish this (I'm not saying it's the best solution). Now it depends whether the requirements you get when you build your package is correct. I somehow remember there was a hidden option or key for this with bundle packages. But this would require checking the mailing-list archive. This email sent to site_archiver(a)lists.apple.com

1 0

Re: handling configuration files
by Fritz Anderson 06 Jul '11

06 Jul '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On 5 Jul 2011, at 7:17 PM, Joe Damato wrote: > Any hints for dealing with config files? I've seen package management > systems in other environments that allow you to mark a packaged file > as a config file so that it is not overwritten on upgrade. Maybe > something like that is possible with package maker and I'm missing it? The situation is probably influenced by the preference that applications not have installers at all, unless privileged system-wide resources like kernel extensions are involved. The preferred way to do it is to carry the default files (or the means to construct them) inside the application package, and have the application install them on first run. * Installation is guaranteed to be in the context of a user who wants to run the app. This includes privileges and whatever configuration might vary among OS versions or users. * The application has unlimited discretion on how to modify and place the configuration files. That includes not replacing existing files, but also preserving user settings while adding new ones, which isn't completely possible in your scenario of ignore-all-or-replace-all. * The application is free to put up initial-configuration UI, and it will be presented to someone who actually knows the answers (remote administrators often don't). * Placement gets done in a privilege environment that matches the one in which the application will actually be used. (I'm sure there are other reasons, but these are the ones that occur to me.) — F _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

handling configuration files
by Joe Damato 06 Jul '11

06 Jul '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=MW20gQKk2jSu9+K36wopNXaGF2/Lozg4gK4yng3KtlQ=; b=K9nJoxt79ExTL3BJAaNMELKFl5O0kNLZbuj4xLdHO0q9XYIRE4F1obTvr9mfw61K3X Es3GNIX16omjshPFg70YyfytPE4jzTo8WuyM+04TiHVEznm6CJSENllWFbrkFxVtu9Zg mJ/jvw66W/fVP+4ASq5Xx3Ufew7v+Rfd38gUs= Hi - The application I'm trying to package comes with a set of default configuration files and plists, however, these files are modified after installation via postinstall so that they suit the user's system (for example, picking a network interface or how much RAM to use for a specific data structure, etc). When the user installs a new version of the packaged application, these configuration files are overwritten. I tried using requirements to test for the existence of the config files and if they exist, skip installing one of the contents that contains the config files, but I was unable to get this to work properly. Doesn't seem like requirements were intended to be used like that. Any hints for dealing with config files? I've seen package management systems in other environments that allow you to mark a packaged file as a config file so that it is not overwritten on upgrade. Maybe something like that is possible with package maker and I'm missing it? Thanks, Joe _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0