August 2008 - Installer-dev

10.5 commandline NSInvalidArgumentException
by Greg Hulands 21 Aug '08

21 Aug '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com I have attached the pmdoc project. Any insight is greatly appreciated, Thanks, 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.… This email sent to site_archiver(a)lists.apple.com Hi, When trying to build on the command line I get the following exception. This is my first installer using PackageMaker 3 as we are trying to convert our build train to 10.5. Leopard1080:MapertureBuild ghulands$ /Developer/usr/bin/packagemaker - d /Users/ghulands/MapertureBuild/AperturePlugins/PhotoPin/Support/ Installer/MaperturePro/Installer.pmdoc -o /tmp/Maperture.pkg 2008-08-20 22:35:43.401 packagemaker[20411:10b] Setting to : 0 (null) 2008-08-20 22:35:43.403 packagemaker[20411:10b] Setting to : 0 com.ubermind.aperture.edit.MaperturePro.pkg 2008-08-20 22:35:43.404 packagemaker[20411:10b] Setting to : 0 com.ubermind.aperture.edit.MaperturePro.pkg 2008-08-20 22:35:43.406 packagemaker[20411:10b] relocate: (null) 0 2008-08-20 22:35:43.407 packagemaker[20411:10b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** - [NSXMLDocument initWithXMLString:options:error:]: nil argument' 2008-08-20 22:35:43.407 packagemaker[20411:10b] Stack: ( 2426093899, 2529845499, 2426093355, 2426093418, 2487484628, 453375, 447724, 436213, 435514, 9990, 9922 ) Trace/BPT trap Leopard1080:MapertureBuild ghulands$ Installer.pmdoc.zip

1 0

Re: Launch Services cache not updated?
by Stéphane Sudre 20 Aug '08

20 Aug '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Aug 20, 2008, at 7:53 PM, Fritz Anderson wrote: I start with an application installed by Installer VISE. I run an Installer.app package that replaces the application. File a bug report so that it can get fixed. It's a known issue AFAIK. _______________________________________________ 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.… The replacement is displayed in the Finder with the original's icon, and Get Info shows the original's version number. I examined the installed Info.plist, and verified that the correct, updated information is there. The application works, demonstrates the updated features, and displays the correct version information in the about box. If I copy the updated application elsewhere, the icon and the displayed version are correct. I assume there is some Launch Services or Finder cache that doesn't get kicked by my installation. What should I be doing about this? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Copying Files in a Plugin
by Stéphane Sudre 20 Aug '08

20 Aug '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Aug 20, 2008, at 7:36 PM, Howard Shere wrote: If you want to copy files, do it from a postflight script for instance. My $0.02 _______________________________________________ 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.… I need to copy some files into the application bundle which will replace some files installed by my installer. I wrote an installer plugin to do the work and the files are being put into the installer bundle on the server before the installer is downloaded by the customer. When the customer runs the installer, it goes through the normal install process and then runs my installer plugin which is supposed to copy files over from the installer bundle to the application bundle. Installer.app runs with the current user id. It doesn't matter if you ask for root authentication or admin authentication. Therefore if you need to change the contents of a root:admin 775 application, you need to belong to the admin group. This email sent to site_archiver(a)lists.apple.com

1 0

Launch Services cache not updated?
by Fritz Anderson 20 Aug '08

20 Aug '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com I start with an application installed by Installer VISE. I run an Installer.app package that replaces the application. Mac OS X 10.4.11 — 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.… The replacement is displayed in the Finder with the original's icon, and Get Info shows the original's version number. I examined the installed Info.plist, and verified that the correct, updated information is there. The application works, demonstrates the updated features, and displays the correct version information in the about box. If I copy the updated application elsewhere, the icon and the displayed version are correct. I assume there is some Launch Services or Finder cache that doesn't get kicked by my installation. What should I be doing about this? This email sent to site_archiver(a)lists.apple.com

1 0

Copying Files in a Plugin
by Howard Shere 20 Aug '08

20 Aug '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: postinstall scripts not executing
by Nigel Kersten 18 Aug '08

18 Aug '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=kERemc86SO88s/ZE6fwDiK1oRKRtDwCZ+yIfmHrqGllbSNuvq8RT+9TMIPPyGroG9r8u67nI+S7gcEUUy1N8pdaFw6nsSis+NuwiVqmUx9jQVVuoIJFHEweK7Z9DJVqy; On Aug 18, 2008, at 8:21 AM, Karl Kuehn wrote: Be a great article for http://afp548.com .... I'm not sure what Scott means by a non-system wide LoginHooks. There's no such thing? All LoginHooks run for all users if LoginHooks have been enabled. You can enable MCX login hooks (and have multiple of them), and those will only run for the user/group/computer/computergroup for which they are set. Actually you can only enable them for Computers and Computer Groups, not for users or groups. They're system-wide, always. There seems to be a lot of confusion around the interweb about the difference between LoginHooks, LoginItems and LaunchAgents.... Any thoughts on where there might be a good place to put a wiki page about this that a number of us can fiddle with to get right? It is annoying that this information is so scattered. We'd love to accept it if you wanted to write something up and I'm more than happy to collaborate on something with 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/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: postinstall scripts not executing
by Karl Kuehn 18 Aug '08

18 Aug '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:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=Gv6qwScl9rckpiziOEYlybMvFedKYn5BXlTM1RzD2so=; b=Go3FOcvb3t/FQg7NaZZLGGttNK/QD7BN4I6BEEfJ3YnpJ54k8+ltEcKmi9DUtXk0UU VkryH3BSjbPpTpLQ9V/bHy1LqeYFv1mqEu9lcekWr5hw012mVicW94PPciqh82bAX9xI vLsLICYdOQDXD7uK3NGvLyXHhvH3Op7IXHA1g= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=Prpa0FYFriQmDqtlIuFgqdcReFlnGUZ6loI3I1/M9p3gvKHYTrp0D4Z8Ey9/q422jP iqD3t35h2da6caBGthuK4qWhJ5D3eclurXgvElMtwwdB72iKgq/iElusrVVuYkz+9Ulg +1cjU3xFsFMXelnxPviam7RusGJaNk3yttHfc= On Aug 18, 2008, at 7:51 AM, Nigel Kersten wrote: -- Karl Kuehn larkost(a)softhome.net _______________________________________________ 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.… LoginHooks are a method that should really only be used in packages for installations where you have control over all the clients who will install your package. If you don't have this control, you should be using a LoginItem (esp now we have a sanctioned method for programmatically adding them) or a LaunchAgent (if you're targeting 10.5 and thus they actually work. Mostly.) Sure, LaunchAgents should be able to cover most of the functionality of LoginHooks, but LoginHooks do run earlier, and have some advantages such as the easy access via $1 of the user who is logging in. To make a small counter-point: LaunchAgents run in the context of the user, so if you need to know the name of the user you just execute `/ usr/bin/whoami`. And most of the things you would do that for are moot since you are already executing as the proper user (~ just works). But there are real advantages to loginhooks as you say (run as root, and run early so you can do things like mount or fiddle with home- directories). I'm not sure what Scott means by a non-system wide LoginHooks. There's no such thing? All LoginHooks run for all users if LoginHooks have been enabled. You can enable MCX login hooks (and have multiple of them), and those will only run for the user/group/computer/computergroup for which they are set. There seems to be a lot of confusion around the interweb about the difference between LoginHooks, LoginItems and LaunchAgents.... Any thoughts on where there might be a good place to put a wiki page about this that a number of us can fiddle with to get right? It is annoying that this information is so scattered. This email sent to site_archiver(a)lists.apple.com

1 0

Re: postinstall scripts not executing
by Nigel Kersten 18 Aug '08

18 Aug '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=ci4RoBlzNAkyN0ykJfzbSWZjdMnuglkAElMyHiVaTXJzKEAPZyz66wfNxIKJ33qw2QlBHea8E2sCFcMWS7sspEwvh6+sOTRAjMBfxY9Pl/tqjVq1KLLdnrEeaxjcbxuG; I think you've summarized it nicely. On Aug 18, 2008, at 6:31 AM, Gignac, Jason (HAS-SAT) wrote: On 8/18/08 Monday, August 18, 2008 -7:09 AM, "Scott Russell" <ScottRussell(a)nd.edu> wrote: The advantage to a kludge like this is that it is not a system-wide loginhook so sysadmins shouldn't complain. However, I think we all know the BEST answer is to write the application correctly to set prefs on first launch from an internal mechanism. Best wishes, Scott -- Dr. Scott Russell IT Support Engineer/Consultant Arts & Letters Computing, Distributed Support Services, Office of Information Technologies, University of Notre Dame Instructor of Horn, University of Notre Dame and Saint Mary's College Assistant Horn, South Bend Symphony Orchestra 234 Decio Hall 574-631-7021 ScottRussell(a)nd.edu http://www.nd.edu/~srussel2/ On Aug 17, 2008, at 5:51 PM, Stéphane Sudre wrote: On Aug 17, 2008, at 7:08 PM, Scott Russell wrote: Instead of login hooks, isn't the correct mechanism going forward a launchd item in /Library/LaunchAgents/ anyway? User-specific, runs at login ... sounds like a login hook to me. *shrug* Can the answer be no? LaunchAgents are only working on 10.5 and later (in 10.4 they are not working correctly at all). Additionally: - LaunchAgents are for repetitive tasks. Setting default preferences is a one-shot operation. - There is no guarantee that a LaunchAgent item will be launched before your app. LoginItems can be launched before a LaunchAgent item. They can already be launched before a LaunchDaemon item. _______________________________________________ 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: _______________________________________________ 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/nigel%40explanatorygap… _______________________________________________ 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.… LoginHooks are a method that should really only be used in packages for installations where you have control over all the clients who will install your package. If you don't have this control, you should be using a LoginItem (esp now we have a sanctioned method for programmatically adding them) or a LaunchAgent (if you're targeting 10.5 and thus they actually work. Mostly.) Sure, LaunchAgents should be able to cover most of the functionality of LoginHooks, but LoginHooks do run earlier, and have some advantages such as the easy access via $1 of the user who is logging in. I'm not sure what Scott means by a non-system wide LoginHooks. There's no such thing? All LoginHooks run for all users if LoginHooks have been enabled. There seems to be a lot of confusion around the interweb about the difference between LoginHooks, LoginItems and LaunchAgents.... Forgive me for being unclear - The problem, I think, that we're running into, is that you have two types of people building packages, here: Developers and Admins. As an Admin myself (I'm not smart enough to be a developer! ;) ), I'm building packages tailored to my specific environment. This means I have the disadvantage of havign no control over the source materials I have to deal with (which leaves me doing things like hacking in preference files to register the product because the developer didn't design for Enterprise deployment, for instance), but with an extremely controlled evironment to roll out my packages to. A developer, essentially, has the opposite set of constraints. Maybe that's the root of this disagreement. I wouldn't 'ship' any of my packages, because they are usually not even my software. And when possible, I CERTAINLY prefer to do things the 'right' way, because it will invariably happen that something in my environment will change later on. But, sometimes, I have to do things the wrong way to get them done. Curse of the Admin. This specific question aside -- in the grander scheme of things, as we go forward, shouldn't we be dropping the idea of loginhooks in favor of LaunchAgents? http://lists.apple.com/mailman/options/installer-dev/jason.gignac%40pearson… > m This email sent to jason.gignac(a)pearson.com This email sent to nigel(a)explanatorygap.net This email sent to site_archiver(a)lists.apple.com

1 0

Re: postinstall scripts not executing
by Gignac, Jason (HAS-SAT) 18 Aug '08

18 Aug '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckBNrCheIxz7UQfuESkeQmYR5M0eg== Thread-topic: postinstall scripts not executing User-agent: Microsoft-Entourage/12.12.0.080729 Forgive me for being unclear - The problem, I think, that we're running into, is that you have two types of people building packages, here: Developers and Admins. As an Admin myself (I'm not smart enough to be a developer! ;) ), I'm building packages tailored to my specific environment. This means I have the disadvantage of havign no control over the source materials I have to deal with (which leaves me doing things like hacking in preference files to register the product because the developer didn't design for Enterprise deployment, for instance), but with an extremely controlled evironment to roll out my packages to. A developer, essentially, has the opposite set of constraints. Maybe that's the root of this disagreement. I wouldn't 'ship' any of my packages, because they are usually not even my software. And when possible, I CERTAINLY prefer to do things the 'right' way, because it will invariably happen that something in my environment will change later on. But, sometimes, I have to do things the wrong way to get them done. Curse of the Admin. On 8/18/08 Monday, August 18, 2008 -7:09 AM, "Scott Russell" <ScottRussell(a)nd.edu> wrote: > The advantage to a kludge like this is that it is not a system-wide > loginhook so sysadmins shouldn't complain. However, I think we all > know the BEST answer is to write the application correctly to set > prefs on first launch from an internal mechanism. > > This specific question aside -- in the grander scheme of things, as we > go forward, shouldn't we be dropping the idea of loginhooks in favor > of LaunchAgents? > > Best wishes, > Scott > -- > Dr. Scott Russell > > IT Support Engineer/Consultant > Arts & Letters Computing, Distributed Support Services, > Office of Information Technologies, University of Notre Dame > Instructor of Horn, University of Notre Dame and Saint Mary's College > Assistant Horn, South Bend Symphony Orchestra > > 234 Decio Hall > 574-631-7021 > ScottRussell(a)nd.edu > http://www.nd.edu/~srussel2/ > > > > > On Aug 17, 2008, at 5:51 PM, Stéphane Sudre wrote: > >> >> On Aug 17, 2008, at 7:08 PM, Scott Russell wrote: >> >>> >>> Instead of login hooks, isn't the correct mechanism going forward a >>> launchd item in /Library/LaunchAgents/ anyway? User-specific, runs >>> at login ... sounds like a login hook to me. *shrug* >> >> Can the answer be no? >> >> LaunchAgents are only working on 10.5 and later (in 10.4 they are >> not working correctly at all). >> >> Additionally: >> >> - LaunchAgents are for repetitive tasks. Setting default preferences >> is a one-shot operation. >> >> - There is no guarantee that a LaunchAgent item will be launched >> before your app. LoginItems can be launched before a LaunchAgent >> item. They can already be launched before a LaunchDaemon item. >> >> >> > > _______________________________________________ > 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/jason.gignac%40pearson…> m > > This email sent to jason.gignac(a)pearson.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: postinstall scripts not executing
by Scott Russell 18 Aug '08

18 Aug '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Best wishes, Scott -- Dr. Scott Russell IT Support Engineer/Consultant Arts & Letters Computing, Distributed Support Services, Office of Information Technologies, University of Notre Dame Instructor of Horn, University of Notre Dame and Saint Mary's College Assistant Horn, South Bend Symphony Orchestra 234 Decio Hall 574-631-7021 ScottRussell(a)nd.edu http://www.nd.edu/~srussel2/ On Aug 17, 2008, at 5:51 PM, Stéphane Sudre wrote: On Aug 17, 2008, at 7:08 PM, Scott Russell wrote: Can the answer be no? Additionally: _______________________________________________ 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.… The advantage to a kludge like this is that it is not a system-wide loginhook so sysadmins shouldn't complain. However, I think we all know the BEST answer is to write the application correctly to set prefs on first launch from an internal mechanism. This specific question aside -- in the grander scheme of things, as we go forward, shouldn't we be dropping the idea of loginhooks in favor of LaunchAgents? Instead of login hooks, isn't the correct mechanism going forward a launchd item in /Library/LaunchAgents/ anyway? User-specific, runs at login ... sounds like a login hook to me. *shrug* LaunchAgents are only working on 10.5 and later (in 10.4 they are not working correctly at all). - LaunchAgents are for repetitive tasks. Setting default preferences is a one-shot operation. - There is no guarantee that a LaunchAgent item will be launched before your app. LoginItems can be launched before a LaunchAgent item. They can already be launched before a LaunchDaemon item. This email sent to site_archiver(a)lists.apple.com

1 0