August 2010 - Installer-dev

Iceberg and Rosetta
by tanya pfeffer 26 Aug '10

26 Aug '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com I am trying to build an installer, using Iceberg, which will run on 10.6 without Rosetta. I've even tried including a Rosetta installer in my meta package. However, I have not had any luck. I'm a total newbie, so any advice is appreciated. Background: I work at a college which requires Symantec anti-visrus software. The Symantec installer requires Rosetta, but doesn't prompt the user to install it. I would like to package Rosetta and the Symantec installer, to make to process easier on our students. -tep _______________________________________________ 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: Issue of Mac Installer with Iceberg
by Stephane Sudre 26 Aug '10

26 Aug '10

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=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=8uyczcWalDpywQ3V9I4e/Q0WmhwpQwpwHfJ5aS5fGnQ=; b=rX+/PjTS4JykQ5qD/tW3pNYNCGQrc+tPpaeLsFxp5gU6FLprGLvdoFWiHXmAqcKJDl x3WAaJinVsZ5f8zHlq/DnV6qOh1zGa0rTEbdSeMVkLpStV73Bzc2sNMA1RuDLi0oSsvz 83rKy5/kROW5fSkne4hUADUIvuQsCoPfLlQ64= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=IJDlZu65l8aVmQ6MGMz3f+KvoqELtubluLDff+XTmtGghFssogBBpv42IezCU5or9M BOgwo25A2r7Uc3OcAGUTuekw/QpYvFMb5AkgedGV7oE7dtWI3EmGR4TBhKznl05JYBal eg/HJ0I+AfJCOw1EC3WQqbQATrNSvK3QaFOS0= AFAIK, Installer.app does not wait for the end of the evaluation of the InstallationCheck "script" to let the user click on the Continue button of the Welcome step. This is why, sometimes, the alert sheet about external stuff appears after the Welcome step. IIRC, I filed a bug report against this some years ago. 2010/8/26 Shaguo <rashaguo(a)gmail.com>: > Hi > > Here is an issue with Installationcheck. > > I add some checks in InstallationCheck and want it to check successfully to > continue installation. > But I still can click continue if InstallationCheck is not finished. Could > you help to give some suggestion to avoid such issue? I want the continue > button in installer dialog can not be clicked before InstallationCheck is > finished. > > I use Iceberg toe create the project in Mac os. > > > -- > Thanks & Best Regards! > > Email:rashaguo@gmail.com > Yahoo:rashaguo@yahoo.com > Blog: http://rashaguo.appspot.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/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

Issue of Mac Installer with Iceberg
by Shaguo 26 Aug '10

26 Aug '10

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=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=l8WCxiMZoO5lm9mBErQ5sX3Us52+YA1fByFiJJFmaBQ=; b=LzuoMVPSKfQHb68ekkPSqzT2lRiMKbM6jvngr2ADRRBmMVbXVaSmLNNpjI9fspXi72 5WGpUDLhanZbh0QXxSlx8dPJicT/qTbENBIR+c9kWTwNVL/C935X5GSRxk1rRtbDUQT9 NZyU34p9d3QX3LwHnfIkQu7hI2xnRqGggn3Go= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=PLg/O7hW1qGJQ3ty+42mayiYCzvFr0eYu6J8XQEfo03VBFLryFPW4fkCr+JvfR9EO+ yJLY71sxAJ+ncHxoriwLtL3pxVhDk/kvrEgtFUnhieHNOxOHhSEXm1JCtdrBbZBg1lOm K4E+ONUlqT5BncZedItLJ8ZlUb5A9oqt32jUc= _______________________________________________ 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: Owner/Group for files put in ~/Library folders
by Greg Neagle 25 Aug '10

25 Aug '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hooray! -Greg On Aug 25, 2010, at 10:16 AM, Howard Moon wrote: > Hi all, > > Greg's reply below led me to ask my bosses why we need to install a file that is not strictly needed and will simply get created if the program options are ever saved. The answer was, well, we don't! So I'm removing that pert of the installation, and now our installers are cleaner (and can be performed remotely, as Greg had mentioned). > > Thanks all (esp. Greg), > Howard > > On Aug 25, 2010, at 9:52 AM, Howard Moon wrote: > >> >> Hi Greg, >> >> the file is simply some program options set on a per-user basis. Our audio plug-in reads it when starting up, and saves it if the user makes changes to the in-program options. We do have default values for all the options in this file, so the file isn't *strictly* required prior to running, but I was asked to give them a default file when installing, so I am. >> >> My question is simple enough: is using root/admin ok, or does my installer (or the script that copies the file from the temp folder to its final location) need to change the owner/group, and if so, to what? >> >> Thanks, >> Howard >> >> On Aug 25, 2010, at 9:31 AM, Greg Neagle wrote: >> >>> Why are you writing to ~/Library/Application Support as part of an install? >>> >>> What happens if a machine has two users, and user1 installs your package, logs out, then user2 logs in and tries to use your software? >>> >>> What happens if the software is installed by an automated process (Casper, LANrev, munki, ARD, etc) and there is no current user? >>> >>> If the file is needed, why can't it be in /Library/Application Support? >>> >>> Or why can't the software generate it on first launch if it is missing from the current user's home folder? This would cover all users of the machine, even those created after the software is installed. >>> >>> -Greg >>> >>> On Aug 25, 2010, at 8:55 AM, Howard Moon wrote: >>> >>>> Hi, >>>> >>>> following the FAQs in the Iceberg User Guide and the advice of folks here, I am able to install a text file into a folder under ~/Library/Application Support (and not overwrite it if it exists). But after installing, I see that the Owner and Group for that file are "root" and "admin", respectively. (Which makes sense, since that's what I set in Iceberg.) >>>> >>>> But if I create a file in that same location myself, (using TextEdit, for example), then the Owner and group are both "Howard". >>>> >>>> Is this a problem? Do I need to set the Owner and Group differently on a user's machine? If so, how do I set them in Iceberg (or in my Postflight script) to be the actual user whose home folder it is stored under? >>>> >>>> Thanks, >>>> Howard >>>> >>>> >>>> _______________________________________________ >>>> 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/greg.neagle%40disneyan… >>>> >>>> This email sent to greg.neagle(a)disneyanimation.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/greg.neagle%40disneyan… > > This email sent to greg.neagle(a)disneyanimation.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: Owner/Group for files put in ~/Library folders
by Howard Moon 25 Aug '10

25 Aug '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi all, Greg's reply below led me to ask my bosses why we need to install a file that is not strictly needed and will simply get created if the program options are ever saved. The answer was, well, we don't! So I'm removing that pert of the installation, and now our installers are cleaner (and can be performed remotely, as Greg had mentioned). Thanks all (esp. Greg), Howard On Aug 25, 2010, at 9:52 AM, Howard Moon wrote: > > Hi Greg, > > the file is simply some program options set on a per-user basis. Our audio plug-in reads it when starting up, and saves it if the user makes changes to the in-program options. We do have default values for all the options in this file, so the file isn't *strictly* required prior to running, but I was asked to give them a default file when installing, so I am. > > My question is simple enough: is using root/admin ok, or does my installer (or the script that copies the file from the temp folder to its final location) need to change the owner/group, and if so, to what? > > Thanks, > Howard > > On Aug 25, 2010, at 9:31 AM, Greg Neagle wrote: > >> Why are you writing to ~/Library/Application Support as part of an install? >> >> What happens if a machine has two users, and user1 installs your package, logs out, then user2 logs in and tries to use your software? >> >> What happens if the software is installed by an automated process (Casper, LANrev, munki, ARD, etc) and there is no current user? >> >> If the file is needed, why can't it be in /Library/Application Support? >> >> Or why can't the software generate it on first launch if it is missing from the current user's home folder? This would cover all users of the machine, even those created after the software is installed. >> >> -Greg >> >> On Aug 25, 2010, at 8:55 AM, Howard Moon wrote: >> >>> Hi, >>> >>> following the FAQs in the Iceberg User Guide and the advice of folks here, I am able to install a text file into a folder under ~/Library/Application Support (and not overwrite it if it exists). But after installing, I see that the Owner and Group for that file are "root" and "admin", respectively. (Which makes sense, since that's what I set in Iceberg.) >>> >>> But if I create a file in that same location myself, (using TextEdit, for example), then the Owner and group are both "Howard". >>> >>> Is this a problem? Do I need to set the Owner and Group differently on a user's machine? If so, how do I set them in Iceberg (or in my Postflight script) to be the actual user whose home folder it is stored under? >>> >>> Thanks, >>> Howard >>> >>> >>> _______________________________________________ >>> 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/greg.neagle%40disneyan… >>> >>> This email sent to greg.neagle(a)disneyanimation.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: Owner/Group for files put in ~/Library folders
by Greg Neagle 25 Aug '10

25 Aug '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Why are you writing to ~/Library/Application Support as part of an install? What happens if a machine has two users, and user1 installs your package, logs out, then user2 logs in and tries to use your software? What happens if the software is installed by an automated process (Casper, LANrev, munki, ARD, etc) and there is no current user? If the file is needed, why can't it be in /Library/Application Support? Or why can't the software generate it on first launch if it is missing from the current user's home folder? This would cover all users of the machine, even those created after the software is installed. -Greg On Aug 25, 2010, at 8:55 AM, Howard Moon wrote: > Hi, > > following the FAQs in the Iceberg User Guide and the advice of folks here, I am able to install a text file into a folder under ~/Library/Application Support (and not overwrite it if it exists). But after installing, I see that the Owner and Group for that file are "root" and "admin", respectively. (Which makes sense, since that's what I set in Iceberg.) > > But if I create a file in that same location myself, (using TextEdit, for example), then the Owner and group are both "Howard". > > Is this a problem? Do I need to set the Owner and Group differently on a user's machine? If so, how do I set them in Iceberg (or in my Postflight script) to be the actual user whose home folder it is stored under? > > Thanks, > Howard > > > _______________________________________________ > 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/greg.neagle%40disneyan… > > This email sent to greg.neagle(a)disneyanimation.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

Owner/Group for files put in ~/Library folders
by Howard Moon 25 Aug '10

25 Aug '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi, following the FAQs in the Iceberg User Guide and the advice of folks here, I am able to install a text file into a folder under ~/Library/Application Support (and not overwrite it if it exists). But after installing, I see that the Owner and Group for that file are "root" and "admin", respectively. (Which makes sense, since that's what I set in Iceberg.) But if I create a file in that same location myself, (using TextEdit, for example), then the Owner and group are both "Howard". Is this a problem? Do I need to set the Owner and Group differently on a user's machine? If so, how do I set them in Iceberg (or in my Postflight script) to be the actual user whose home folder it is stored under? Thanks, Howard _______________________________________________ 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: How to not install a file if it exists?
by Howard Moon 25 Aug '10

25 Aug '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Never mind, I sussed it out. On Aug 25, 2010, at 7:27 AM, Howard Moon wrote: >> >>> Maybe a stupid question, but I can't find the answer... >>> >>> I'm using Iceberg to create a meta-package installer, and have one component that installs a single file to the user's Application Support folder hierarchy. But if the user already has that file there, I don't want to overwrite it (because it contains user settings they might want to keep, and not get them overwritten with the default settings). >>> >>> How do I keep a single file from being overwritten if it already exists? >>> >>> Thanks, >>> Howard >> >> Common ways to do this: >> >> -create/install the file using your application on first-run, if it finds no file present >> -install the file in a temporary folder, then in a post-install script, move it to the correct location if it finds no file present >> > > Where can I find info on how to do that 2nd method? I've done very little script writing (but am familiar with working at the command-line level). But I don't know how to use Iceberg to put the file into a temporary directory in the first place. Are there any good web sources for examples of doing this? > > Thanks for any help... > -Howard > > _______________________________________________ > 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/howard%40antarestech.c… > > This email sent to howard(a)antarestech.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: How to not install a file if it exists?
by Howard Moon 25 Aug '10

25 Aug '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com > >> Maybe a stupid question, but I can't find the answer... >> >> I'm using Iceberg to create a meta-package installer, and have one component that installs a single file to the user's Application Support folder hierarchy. But if the user already has that file there, I don't want to overwrite it (because it contains user settings they might want to keep, and not get them overwritten with the default settings). >> >> How do I keep a single file from being overwritten if it already exists? >> >> Thanks, >> Howard > > Common ways to do this: > > -create/install the file using your application on first-run, if it finds no file present > -install the file in a temporary folder, then in a post-install script, move it to the correct location if it finds no file present > Where can I find info on how to do that 2nd method? I've done very little script writing (but am familiar with working at the command-line level). But I don't know how to use Iceberg to put the file into a temporary directory in the first place. Are there any good web sources for examples of doing this? Thanks for any help... -Howard _______________________________________________ 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

Update Folder Contents in PackageMaker
by Paul Cook 24 Aug '10

24 Aug '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com How do you get PackageMaker (PM) to update or refresh the contents of a folder of stuff to be installed? As part of the process, we've updated the contents of of what we want installed in a particular location. While the contents of the folder have been updated, PM still seems to only know about what was there when we did the original "Add Contents..." The only way that I can get it to update is to "Add Contents..." again and delete the old one. Surely there must be a better way? Thanks for any help, Paul _______________________________________________ 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