October 2008 - Installer-dev

Re: easy uninstaller solution
by Bill Janssen 23 Oct '08

23 Oct '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Adam Fisk <a(a)lastbamboo.org> wrote: > Once you've got the application bundle set up, you just need to > update and maintain the bash script and never worry about building the > bundle or editing the AppleScript (a bit of a pain) again since the > AppleScript will always just call whatever's in your bash file. I find writing a little Cocoa-Python script works pretty well, too, if you need a GUI to your uninstaller. Bill _______________________________________________ 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

easy uninstaller solution
by Adam Fisk 23 Oct '08

23 Oct '08

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:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition:x-google-sender-auth; bh=kEZexfub2bvQExLtZRDksjoXdz1Pnp+onl10wr2Tqsg=; b=Shc50eY7t0iEVzVvokzSZEtjyzcJ6K8Sm3TJedHBhmjplJq0ivkAtWDaPAIxsYJwnq rSmZAJ0IALAAcLFDN4CjCnMiQOgQITJ3xicx1BGdcnk7XzqXE3zrNV9H05TOSVjd/3Tr qRCgxo5KEQ3W4q3ENx/A4/0Fi0C6s80TEgZ2c= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition:x-google-sender-auth; b=daLeN6yrKeGo40tHLN7dQ1mj1D/yAP5+PEJBhqfnZkikRjiWU1dymisdLUX+Cp1HMd h6/QwGEkE9V1+onA5G4hcRs0ZyQLkI+KdRVVzqAfsJcjajhClVgmuR/DsCilR7O+xjK7 ovE1z2yf6WiGIqb8DqkqXO6e/TgfgV0/RN22Y= Hi Everyone- I just posted a really great (I think) uninstaller solution on my blog I think people here may find useful. Basically, you just perform your entire uninstall in a bash script that's called from an AppleScript application bundle (so the user can double click it). Once you've got the application bundle set up, you just need to update and maintain the bash script and never worry about building the bundle or editing the AppleScript (a bit of a pain) again since the AppleScript will always just call whatever's in your bash file. The post is here: http://adamfisk.wordpress.com/2008/10/22/osx-uninstallers-the-easy-way/ Any feedback in the comments is most welcome. There may very well be a better way of doing this I'm unaware of. -Adam -- http://www.littleshoot.org P2P Meets Web 2.0 _______________________________________________ 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: Destination Select intermittently displays
by Luke Bellandi 22 Oct '08

22 Oct '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Ack0gCwK5Z6NJn37TjyO0Ai2oArDZgAAtzH5 Thread-topic: Destination Select intermittently displays User-agent: Microsoft-Entourage/12.10.0.080409 _______________________________________________ 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

Destination Select intermittently displays
by Riffel, Allen 22 Oct '08

22 Oct '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Ack0gCwK5Z6NJn37TjyO0Ai2oArDZg== Thread-topic: Destination Select intermittently displays _______________________________________________ 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: problem with Iceberg hanging?
by Bill Janssen 22 Oct '08

22 Oct '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Bill Janssen <janssen(a)parc.com> wrote: > I've given up on PackageMaker, and switched over to using Iceberg > instead, to build my metapackage with. However, I've got this problem > that Iceberg occasionally hangs when I tell it to "Build". It's not > stuck; I can still do things with the app, it's just that the build > doesn't progress. No idea why -- there appear to be no Iceberg log > files or error messages, but I do notice in the console log that the > automounter seems to be enumerating all possible mount points -- don't > know if Iceberg is causing that. I found a temp file in the root of the NFS-mounted filesystem I was storing my .packproj file on, with some files named "(Iceberg Attempting to Save Project...)" or some such. I deleted this whole temp tree, restarted Iceberg, and got rid of the hang. I'll document this better if it happens again. Bill _______________________________________________ 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: A question about locations within a package, vis-à-vis postinstall script
by Greg Neagle 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Oct 21, 2008, at 3:16 PM, OSullivan, Steve wrote: I have changed my ditto line to use $1, so that it now reads: ditto $1/Resources/com.product.launchd.engine_osx.plist /Library/LaunchDaemons/ If it's a shell script, it probably should read -Greg _______________________________________________ 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.… And yet, ditto responds that it cannot 'get real path for source'. ditto "$1/Contents/Resources/com.product.launchd.engine_os.plist" / Library/LaunchDaemons/ so that the $1 variable gets interpolated into the pathname. And "Contents" should be part of the path. I have been learning this piecemeal, and working outside of the GUI. How would you suggest that I get the com.product.launchd.engine_osx.plist file into the bom and archive? Using whatever method you are currently using to get all your other files into the bom and archive.payload. This email sent to site_archiver(a)lists.apple.com

1 0

Re: A question about locations within a package, vis-à-vis postinstall script
by OSullivan, Steve 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckzyqKHH1K8Mi6xyU6G9/KKKCK+DQ== Thread-topic: A question about locations within a package, vis-à-vis postinstall script User-agent: Microsoft-Entourage/12.12.0.080729 Greg, Thank you very much for your correspondence. I have changed my ditto line to use $1, so that it now reads: ditto $1/Resources/com.product.launchd.engine_osx.plist /Library/LaunchDaemons/ And yet, ditto responds that it cannot 'get real path for source'. I have also removed the sudos from the script and everything else still works even without them.... I guess that they were a security risk? I have been learning this piecemeal, and working outside of the GUI. How would you suggest that I get the com.product.launchd.engine_osx.plist file into the bom and archive? Thanks for any and all assistance! Regards, Steve O'Sullivan On 10/21/08 11:33 AM, "Greg Neagle" <Greg.Neagle(a)disneyanimation.com> wrote: > $1: Full path to the installation package the Installer application > is processing. For example: /Volumes/Users/michelle/Desktop/ > Levon.mpkg > > So: > > ditto $1/Contents/Resources/com.company.launchd.engine_OS.plist / > Library/LaunchDaemons/ > > Don't use sudo in your postinstall scripts. > And - any reason the launchd plist isn't simply in the archive and bom? > > Try to avoid postinstall (and preinstall) file copying if at all > possible. Ideally the bom should tell the truth as far as what files > were installed and/or replaced by your package. > > -Greg > > > On Oct 21, 2008, at 11:19 AM, OSullivan, Steve wrote: > >> Good morning all, >> >> I am creating an installer package using PackageMaker 3.0.2 from the >> command >> line. >> >> I am running a postinstall script that overall seems to work well >> (it is >> triggered and most of its commands are carried out.) >> >> The problem lies in the fact that I am trying to copy a launch >> daemon plist >> from the package to /Library/LaunchDaemons, and I cannot seem to >> find the >> proper syntax to tell the script where the launch daemon plist is >> located in >> the installer. >> >> Things are laid out like this (examining the package with Pacifist): >> >> engine.pkg >> pkgbaseengine.pkg >> scripts >> postinstall >> Resources >> launch daemon plist >> >> In my postinstall script, I am using the following line to try and >> place the >> launch daemon plist in the appropriate place which so far fails: >> >> sudo ditto ../Resources/com.company.launchd.engine_osx.plist >> /Library/LaunchDaemons/ >> >> As of right now, I do not know how to properly identify the starting >> location of the launch daemon to be able to copy it into the >> /Library/LaunchDaemons directory. >> >> I really appreciate any and all thoughts! >> >> TIA, >> >> Steve O'Sullivan >> >> _______________________________________________ >> 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… >> ation.com >> >> 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: A question about locations within a package
by Aaron London 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckzqeVoaQ9kZhKuQeeEWv0iG3ymXwAARJnQ Thread-topic: A question about locations within a package >> In my postinstall script, I am using the following line to try and place the launch daemon plist in the appropriate place which so far fails: sudo ditto ../Resources/com.company.launchd.engine_osx.plist /Library/LaunchDaemons/ As of right now, I do not know how to properly identify the starting location of the launch daemon to be able to copy it into the /Library/LaunchDaemons directory. << First of all, why not install the launch daemon plist as part of the payload. Just put the file at <payload root>/Library/LaunchDaemons/com.company.launchd.engine_osx.plist. Or create a separate component package that installs the file to the component root /Library/LaunchDaemons. To figure out your cwd in the postinstall script, just add an "echo `pwd`" before the ditto call. It should probably be "sudo ditto Contents/Resources/ com.company.launchd.engine_osx.plist /Library/LaunchDaemons" as I seem to recall that scripts inherit the bundle root as their cwd. -A _______________________________________________ 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: A question about locations within a package, vis-à-vis postinstall script
by Greg Neagle 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com So: Don't use sudo in your postinstall scripts. And - any reason the launchd plist isn't simply in the archive and bom? -Greg On Oct 21, 2008, at 11:19 AM, OSullivan, Steve wrote: Good morning all, Things are laid out like this (examining the package with Pacifist): engine.pkg pkgbaseengine.pkg scripts postinstall Resources launch daemon plist sudo ditto ../Resources/com.company.launchd.engine_osx.plist /Library/LaunchDaemons/ As of right now, I do not know how to properly identify the starting location of the launch daemon to be able to copy it into the /Library/LaunchDaemons directory. I really appreciate any and all thoughts! TIA, Steve O'Sullivan _______________________________________________ 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… _______________________________________________ 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.… $1: Full path to the installation package the Installer application is processing. For example: /Volumes/Users/michelle/Desktop/ Levon.mpkg ditto $1/Contents/Resources/com.company.launchd.engine_OS.plist / Library/LaunchDaemons/ Try to avoid postinstall (and preinstall) file copying if at all possible. Ideally the bom should tell the truth as far as what files were installed and/or replaced by your package. I am creating an installer package using PackageMaker 3.0.2 from the command line. I am running a postinstall script that overall seems to work well (it is triggered and most of its commands are carried out.) The problem lies in the fact that I am trying to copy a launch daemon plist from the package to /Library/LaunchDaemons, and I cannot seem to find the proper syntax to tell the script where the launch daemon plist is located in the installer. In my postinstall script, I am using the following line to try and place the launch daemon plist in the appropriate place which so far fails: This email sent to greg.neagle(a)disneyanimation.com This email sent to site_archiver(a)lists.apple.com

1 0

Setting up installation requirements
by R. Padraic Springuel 21 Oct '08

21 Oct '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.17 (Macintosh/20080914) Any help on the matter would be greatly appreciated. _______________________________________________ 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 I'm making an installation package for the first time and am trying to figure out how to setup the installation requirements. In particular, I'd like to setup the installer to check that Perl 5.8 or higher is installed on the user's system. My first thought on this was to do a "File Exists" check for /Library/Perl/5.8.6/AppendtoPath, and raise a warning (but not prevent install) if the file didn't exist (i.e. the installer would look for the same version of perl that I have and if it wasn't there, warn the user to check that their own version was more recent). However, that recommendation caused an install fail on a system with perl 5.8.8, which means it was being interpreted as a requirement, not a recommendation (installation worked fine on another system with perl 5.8.6). Since I don't know why a recommendation would cause an install fail, I thought to look for something whose path was a bit less dependent on version. My second though was to check for the existence of /usr/bin/perl, but that's versionless. So, while it will check to make sure perl is present on the system, it's not checking on the version number. I do know that typing "perl -V:version" at the command line will return "version='#versionnum#';" but I can't seem to figure out how to incorporate that into a requirements check in the PackageMaker interface. The Apple documentation seems to indicate that I can write an executable that will perform the check, but it isn't real clear about how to go about doing this, nor how to tell PackageMaker to use the script. I'm working on OS 10.4.11 with PackageMaker 2.1.1, if that makes a difference in how I do this. -- R. Padraic Springuel smime.p7s

1 0