September 2008 - Installer-dev

Re: Permissions on 10.5.4 & packagemaker 2.1.1
by Bill Royds 23 Sep '08

23 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.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: Version control in Installer Packages
by Scott Amory 23 Sep '08

23 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Sep 22, 2008, at 11:00 PM, Ulf Dunkel wrote: So we have set up the "Requirements" as follows: Required: required Pass if: true Description: Target OS Version: is greater than or equal to '10.4.5' This works fine when I test it on my Leopard machine (of course). if(!(my.target.systemVersion.ProductVersion >= '10.4.5')) { Scott Thank you in advance, UlfDunkel _______________________________________________ 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.… Our iCalamus installer for CD shipment has been set up in a way that it should check the customer's Mac OS X version first. But now a customer complained that it didn't work on his Tiger machine with 10.4.11. How the heck are values compared in "Requirements"? I guess they are compared as strings (where "10.4.11" is lower than "10.4.5"). Can someone confirm this as a bug - or did we something wrong? Hi Ulf, I'm sorry to say that I think that this is a bug in PackageMaker. I set up a test as you described and looked at the distribution file that it created. The check that it sets up looks like this: On the surface that might look correct but it isn't. In a situation when comparing this to 10.4.10 or higher it's going to give the incorrect answer. To be correct it would have to look something like this: if(-1 == system.compareVersions(my.target.systemVersion.ProductVersion, '10.4.5')) { Called this way it should properly compare the versions. The return code of the compareVersions function is -1 for less than 0 for equal and 1 for greater than. In your situation I would suggest you manually change the distribution after creating it through PM. And please file a bug for this. _______________________________________________ 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/samory %40apple.com This email sent to samory(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Permissions on 10.5.4 & packagemaker 2.1.1
by Annette Brooks 23 Sep '08

23 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Ackdou3mhVvm9ZpSgkmSLnE5vFcY+w== Thread-topic: Permissions on 10.5.4 & packagemaker 2.1.1 _______________________________________________ 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

Version control in Installer Packages
by Ulf Dunkel 23 Sep '08

23 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Organization: invers Software & DSD.net User-agent: Thunderbird 2.0.0.17pre (Windows/20080922) So we have set up the "Requirements" as follows: Required: required Pass if: true Description: Target OS Version: is greater than or equal to '10.4.5' This works fine when I test it on my Leopard machine (of course). Can someone confirm this as a bug - or did we something wrong? Thank you in advance, UlfDunkel _______________________________________________ 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.… Our iCalamus installer for CD shipment has been set up in a way that it should check the customer's Mac OS X version first. But now a customer complained that it didn't work on his Tiger machine with 10.4.11. How the heck are values compared in "Requirements"? I guess they are compared as strings (where "10.4.11" is lower than "10.4.5"). This email sent to site_archiver(a)lists.apple.com

1 0

Re: Password protection on Installer Package
by Bill Coderre 22 Sep '08

22 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Sep 22, 2008, at 5:36 AM, Adil Saleem wrote: Is it possible to put a password on the installer package ? So that only i can (or anybody who knows the password) can install using that package ? I have PackageMaker 3.0.2 On Sep 22, 2008, at 4:31 AM, David Watson wrote: Not as far as I know, but what you can do is to put it inside an encrypted DMG. You can do this manually through Disk Utility, or do it from the command line: hdiutil create -passphrase "$PASSWORD" -srcfolder $SOURCEFOLDER - volname $"VOLNAME" -encryption AES-128 $OUTPUT Anyone can "show package contents" and double-click the Archive file and get the contents out. (Things are only slightly more complex with flat packages.) So making an encrypted disk image is about as good as it gets. _______________________________________________ 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: Password protection on Installer Package
by David Watson 22 Sep '08

22 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Sep 22, 2008, at 5:36 AM, Adil Saleem wrote: Hi, Thank You _______________________________________________ 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/dwatson%40mimvista.com -- David Watson Director of Software Development MIMvista Corp Direct: 216-455-0604 Toll-Free: 866-421-2536 www.mimvista.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.… Not as far as I know, but what you can do is to put it inside an encrypted DMG. You can do this manually through Disk Utility, or do it from the command line: hdiutil create -passphrase "$PASSWORD" -srcfolder $SOURCEFOLDER - volname $"VOLNAME" -encryption AES-128 $OUTPUT Is it possible to put a password on the installer package ? So that only i can (or anybody who knows the password) can install using that package ? I have PackageMaker 3.0.2 This email sent to dwatson(a)mimvista.com This email sent to site_archiver(a)lists.apple.com

1 0

Password protection on Installer Package
by Adil Saleem 22 Sep '08

22 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=kFcZoBhvaJkSzxw8xIZS7i5Ndnzo9va8GgU5pi4QQ3leMVY3P9QTF3sXhXWNKhZ19cJkbknPPlhBOvzsQn/gww0tQiEXSU2wpOraFz2X1sU2jmPJ8FJzqHVwfGwLSb8fpL9pHv4bl47nKTM/+phxyf0B1JJCKzCXCH6yaSFRSFk=; _______________________________________________ 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: Apple Installer package questions
by Nigel Kersten 20 Sep '08

20 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=explanatorygap.net; h=Received:Cc:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer:X-Identified-User; b=QdR40Kn+afpEDoKOi1FbsjmwE3Oti/wAdlj5IgBiFfhAQ/pgBMaGSluPrESA/9bJFqykAgynDuH8tXARo8BK0eR9UAW4nvINVMyAXkBEiLMNDtQ1Ktmhr3zz4MEzk+/h; On Sep 19, 2008, at 5:26 PM, Fred Licht wrote: --target is exposed as the $3 argument to your install scripts. _______________________________________________ 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.… Hey Everyone, Forgive me if I am about to ask questions others have asked before. I use the CLI installer for almost all of my work. So leveraging functions the GUI provides at the CLI are important. 1. If I set the default install location to "/" stating it is required, will the CLI installer respect that package setting? 2. If I manually assign the -target flag on the CLI installer to give it a different location, will the CLI installer send me a warning or error, or just allow me to override where it is to be installed? 3. If the CLI installer "-target" command is perceived as changing the install location, how would I extract this new location in the pre-flight or preinstall scripts? The install location is relative to the mountpoint of the volume you are installing onto. The --target flag allows you to specify a different volume. It's analogous to choosing the volume in the GUI installer, not to setting the install location. This email sent to site_archiver(a)lists.apple.com

1 0

Apple Installer package questions
by Fred Licht 20 Sep '08

20 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thanks, Fred _______________________________________________ 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.… Hey Everyone, Forgive me if I am about to ask questions others have asked before. I use the CLI installer for almost all of my work. So leveraging functions the GUI provides at the CLI are important. 1. If I set the default install location to "/" stating it is required, will the CLI installer respect that package setting? 2. If I manually assign the -target flag on the CLI installer to give it a different location, will the CLI installer send me a warning or error, or just allow me to override where it is to be installed? 3. If the CLI installer "-target" command is perceived as changing the install location, how would I extract this new location in the pre- flight or preinstall scripts? This email sent to site_archiver(a)lists.apple.com

1 0

RE: previous version clobbering newer version?
by Lisa Weimer 19 Sep '08

19 Sep '08

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Thread-index: AcjSWKfjPD/g1I6XRzuyIFH/ocsKDBHfC6MAAAFB5M0AJaE4AA== Thread-topic: previous version clobbering newer version? Thank you for the idea Pradeep. I was really hoping there was some way to tell the package containd in a metapackage to do the Right Thing-- when an old package encounters a new one, just leave the newer packages completely alone. I was hoping I had just missed a setting something in file or something. I will try the installation check scripts method and see if it does what I need it to do. :) Lisa -----Original Message----- From: Pradeep Kumar Udupi [mailto:pradeep@robosoftin.com] Sent: Thursday, September 18, 2008 4:00 PM To: Lisa Weimer; installer-dev(a)lists.apple.com Subject: Re: previous version clobbering newer version? I had encountered a very similar problem recently. The receipt based version check of pkgs does not happen when the pkgs are installed from a metapackage. It just installs all the pkgs that are listed in default install unless blocked by the pkg's check tools. The man page for 'installer' tool states, "The installer command is used to install Mac OS X installer packages to a specified domain or volume. The installer command installs a single package per invocation, which is specified with the -package parameter ( -pkg is accepted as a synonym). It may be either a single package or a metapackage. In the case of the metapackage, the packages which are part of the default install will be installed unless disqualified by a package's check tool(s)." One way to solve this issue is to use InstallationCheck scripts to control the installation. In the InstallationCheck script you can check if a previous version of that pkg is installed or not and if installed do a version check of the receipt pkg and the one that's installed. - pradeep > Hi all, > Has anyone ever seen this behaviour, if so how did you fix it? > > Product 1 contains > Package A.pkg version 1.0.2.0 is installed on the system > Package product 1.pkg > > Product 2 contains > Package A.pkg version 1.0.1.0 > Package product 2.pkg > > Product 1 is installed on the system. I then install Product 2 after > product 1 has been installed. Note that product two has an older version > of package A.pkg. > > My problem is that the installer when installing package A.pkg version > 1.0.1.0 will remove 'obsolete' files that are actually the newer files > of Package A version 1.0.2.0. (mostly language and support documents) > while refusing to install the older version of the app (which has a > versions.plist). The end result is you have a new app with missing > support files that have been removed. > > The odd thing is if I remove package A completely from the metapackage, > and install them stand alone, the correct thing happens: The install > halts and says a newer version exists on the system. > > Is there some magic .plist file that controls this behaviour? Why does > it only happen when the package is in the metapackage? > > Any thoughts? > > Thanks, > Lisa > > > Lisa Weimer > Build/Install > SMART Technologies > > _______________________________________________ > 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/pradeep%40robosofti n.com > > This email sent to pradeep(a)robosoftin.com > ----------------------------------------------- Robosoft Technologies - Come home to Technology Disclaimer: This email may contain confidential material. If you were not an intended recipient, please notify the sender and delete all copies. Emails to and from our network may be logged and monitored. This email and its attachments are scanned for virus by our scanners and are believed to be safe. However, no warranty is given that this email is free of malicious content or virus. _______________________________________________ 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