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

installing in the user's home directory?
by Rich Morin 02 Apr '11

02 Apr '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com I'm trying to use PackageMaker to create an installer that unpacks a directory tree into a sub-directory of the user's home directory. I'd like the permissions and ownership to be "normal" (eg, allow the user to read and write files, but not everyone on the system). So, the usual advice about setting things to root/admin isn't really appropriate and I certainly don't want things to be set to MY uid on someone else's machine. Suggestions? -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume rdm(a)cfcl.com http://www.cfcl.com/rdm/weblog +1 650-873-7841 Software system design, development, and documentation _______________________________________________ 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: installing in the user's home directory?
by Colin Cornaby 02 Apr '11

02 Apr '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com This isn't really simple. You've got to install into a temp location, and then copy the file into place in the user directory with a script, and then use the script to fix the permissions (if you're nice, not simply setting the permissions to 777...) It's been a bit so I don't recall offhand the trick I used to line up the permissions properly. It involved reading the permissions of the parent folder and copying them to the installed files. I'm sure someone else here can help you with that. If you only need to support 10.5 and higher, I believe the 10.5 package format has an added feature that allows you to install into a home directory. On Apr 2, 2011, at 12:40 AM, Rich Morin wrote: > I'm trying to use PackageMaker to create an installer > that unpacks a directory tree into a sub-directory of > the user's home directory. > > I'd like the permissions and ownership to be "normal" > (eg, allow the user to read and write files, but not > everyone on the system). So, the usual advice about > setting things to root/admin isn't really appropriate > and I certainly don't want things to be set to MY uid > on someone else's machine. > > Suggestions? > > -r > -- > http://www.cfcl.com/rdm Rich Morin > http://www.cfcl.com/rdm/resume rdm(a)cfcl.com > http://www.cfcl.com/rdm/weblog +1 650-873-7841 > > Software system design, development, and documentation > _______________________________________________ > 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/colin.cornaby%40mac.com > > This email sent to colin.cornaby(a)mac.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: Mysterious .app/Finder corruption?
by Eli Bach 01 Apr '11

01 Apr '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=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=0azyL8597alpKcfy81ou3SnP2iHzRAOy56bXTDSfDEA=; b=LNC2UbdyF1CmSLABB/gRVbT+XhSmbkDf6sRR8neLcSawmGSZLxFPr1Hy0LlqxHwraC pm7FXsAq292OQVE+qMsuOdN+IPTSpfrD6yYiYhEOhISZWIN775wOBMPBnVz8Y/lLaTil QfLD8bu4s0cZHRLyrXab6ZI5jkmZH3ZO4rk1M= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=oN+EF6A6U5sMu+6qkuFlKWaV4GTqSlkyX9KBd+UzEfyBQKt4RcUTPgQk5DyQocq2Zj 0Vq4ZwjPG3nZL+n5RobzJYl4Ecm0BdxTqjYNMVYtnjDND7DqOgDApjDkhQ7wGar0A2DA jEzV0eFgmKdBaiSL7rQJT2FhdELPjVRjmb1QQ= On Apr 1, 2011, at 3:35 PM, Andy O'Meara wrote: > Will keep trying to crack this! Ugh, it just sucks to burn so much time on crap like this.. Andy, Is anything showing up in Console when you launch it with the Finder? Eli _______________________________________________ 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: Mysterious .app/Finder corruption?
by Joseph Chilcote 01 Apr '11

01 Apr '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=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=DapqribraXIN+8m5o+yNz2revxltAOp8fRFvxNZpFvM=; b=OTFygDfR9/aOGDQ379xwQ5zt4yWuXzVtEhsnKa+IwuCIuYNyeWM8uUtkR5IN4VoCk7 xXLWfgLy7/Y3lUbsazKfE/r9w5NiOui+9NRmYWQ78hYTGMMGftfsuovRiJflNhb+OxEP FUkd4Z8stQh+rYMdlcV49TI7PkysggBbKQvrQ= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=n1UsR7OCrPOpXry7rxNaDNfe8+UohdXPuIyEgKQuCfVTV6VEwsVdztd+Pstmd4cvKy wAIEp0c6idi6gMPW7jKRplQyULoQUscTGe0DQt1x4YzlV20jWGde+wV9GLTfFd2sRr8y CLmaAzTBSu/u2crdBiseDzfpOSz2GJi5ZFLsQ= On Fri, Apr 1, 2011 at 2:48 PM, Andy O'Meara <andrew.omeara(a)soundspectrum.com> wrote:> >> Also, since you can get it to work by >> launching the App before packaging it, have you tried trapping for >> what changes when you launch it on your build machine? Sounds like >> this problem exists even before it's being packaged. >> > Sorry, I'm having trouble following you here. The app seems to be fine by every measure before getting packaged since there isn't a case where it had problems before getting packaged. It's only after the package installer is run where it has problems following a double-click launch. My bad, I mis-interpreted your original email to mean that if you launch the app on the build machine and then package it, then the problem does not appear. I see now that you were just proving that the app worked. If it's indeed a problem that is specific to that folder, what if you put something else in there, like say, Firefox? Will Firefox not load? If you deploy the app directly to the Applications folder without the subdirectory, does it error? Might be time to dust off your one of your developer tech support incidents. --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

Re: Mysterious .app/Finder corruption?
by Andy O'Meara 01 Apr '11

01 Apr '11

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com > Also, since you can get it to work by > launching the App before packaging it, have you tried trapping for > what changes when you launch it on your build machine? Sounds like > this problem exists even before it's being packaged. Sorry, I'm having trouble following you here. The app seems to be fine by every measure before getting packaged since there isn't a case where it had problems before getting packaged. It's only after the package installer is run where it has problems following a double-click launch. I just tried the following, whew: using the finder, if I move the if I move the installed foo.app from /Applications/foo/ (which had probs when double clicked) to the desktop, and then move the foo.app that was used to build the package (which has never shown an issue), the newly moved foo.app now shows the same problem, ugh. If I move that foo.app anywhere else, it starts working. So it's as if the Finder has something cached for that specific pathname and is taking different action somehow on a finder-based launch. Hmmm! _______________________________________________ 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: Mysterious .app/Finder corruption?
by Andy O'Meara 01 Apr '11

01 Apr '11

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Hi Joe, thanks a ton for writing -- I think I've already gotten a few more grey hairs from trying to figure this out. On further experimentation, I've discovered that if I launch the app from the command line (from any dir), it runs properly (either using open -a foo.app or ./foo.app/Contents/MacOS/foo). If I simply double click the same app, it doesn't work -- argh Apple! I wish like hell I could provide more than "it doesn't work" but I can't repro it with the debugger attached (no idea why). The best I have is that the app seems to run ok, but when it loads our bundle and we use CFBundleGetFunctionPointerForName() to fetch code symbols, we keep getting NULL. Keep in mind that if the app is run from the command line or a different dir, this does not occur. This leads me to think the Finder/OS is somehow confused when it goes to fetch symbols from the bundle. This app is only a 32-bit universal binary and the bundle is a 32+64 bit universal binary, so I tried building the app as a 64 bit universal binary but the problem persisted. Will keep trying to crack this! Ugh, it just sucks to burn so much time on crap like this.. Thanks, Andy On Apr 1, 2011, at 3:28 PM, Joseph Chilcote wrote: > On Thu, Mar 31, 2011 at 5:30 PM, Andy O'Meara > <andrew.omeara(a)soundspectrum.com> wrote: >> Hey everyone, >> >> I've been trying to get insight into what appears to be an inane bug either within the OS X package installer or the Finder. >> >> We use a build script that builds all our .bundles and .apps and then calls package maker via the command line to make our .pkg. Our package creates a new dir in the Applications dir (if it doesn't already exist), and expands the .app into this directory. What's happening is that after the installer runs our package, our .app fails to load our bundle. Yet if I run the .app that the package was given (ie. if I run the app before it gets sucked into the pkg), the app runs fine -- it's as if somehow the .app created by the installer is somehow not right. > > Hi Andy, > > Not sure I follow what you mean by the app failing to load the bundle, > but it could be that launchservices is not properly registering the > app. I've seen this behavior when installing apps into a subdirectory > of /Applications. I've been able to fix it by dropping a symlink in > /Applications, or even simply navigating to the parent directory of > the app itself and launching it from there. But it sounds like even > that's not working for you. Also, since you can get it to work by > launching the App before packaging it, have you tried trapping for > what changes when you launch it on your build machine? Sounds like > this problem exists even before it's being packaged. > > If I were you, I'd reduce the complexity of your package to its > simplest state. Package just your App (after triple-checking the > permissions) to install only into /Applications. Does that work? > Include your pre-install script. Does that work? Add the > subdirectory. Etc, etc. Perhaps this process will lay bare the > problem. > > Best regards, > > --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/andrew.omeara%40sounds… > > This email sent to andrew.omeara(a)soundspectrum.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: Mysterious .app/Finder corruption?
by Joseph Chilcote 01 Apr '11

01 Apr '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=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=ywBjEgJQY3Wc0LVbvrqmCA3KoKXMj8+4lgAATh2H/HM=; b=qcbO9EIKtwQCXAOeocVP15SSOx5840O41esx4Ix7sMCwbbpIw9gFZRT3olpQodd8xB 1jSW9ZuWChrJwECkAw/AFWBKSnhOXGL2M2QHN86TYezeVRcRl3z0GsbbP54AlB8eEImI WDZzOU2eyRj1nZIACCes0rkVoq0U7oMQT4Pik= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=nXeKyxU+J52mwewE0tk3EGvgQQELTL0cZICFuA231U+R51//sgnntLnz64ixpfgIMn Rm0N1gn+kcnfGRtjgOF9vMlENbGwgG6asdhD5TWg+0+UNPxPLzBpdJTICdCzr75q1Jza D44rwjuzHnn61lHxOxrhPXooFQx8Rsw6bNOYE= On Thu, Mar 31, 2011 at 5:30 PM, Andy O'Meara <andrew.omeara(a)soundspectrum.com> wrote: > Hey everyone, > > I've been trying to get insight into what appears to be an inane bug either within the OS X package installer or the Finder. > > We use a build script that builds all our .bundles and .apps and then calls package maker via the command line to make our .pkg. Our package creates a new dir in the Applications dir (if it doesn't already exist), and expands the .app into this directory. What's happening is that after the installer runs our package, our .app fails to load our bundle. Yet if I run the .app that the package was given (ie. if I run the app before it gets sucked into the pkg), the app runs fine -- it's as if somehow the .app created by the installer is somehow not right. Hi Andy, Not sure I follow what you mean by the app failing to load the bundle, but it could be that launchservices is not properly registering the app. I've seen this behavior when installing apps into a subdirectory of /Applications. I've been able to fix it by dropping a symlink in /Applications, or even simply navigating to the parent directory of the app itself and launching it from there. But it sounds like even that's not working for you. Also, since you can get it to work by launching the App before packaging it, have you tried trapping for what changes when you launch it on your build machine? Sounds like this problem exists even before it's being packaged. If I were you, I'd reduce the complexity of your package to its simplest state. Package just your App (after triple-checking the permissions) to install only into /Applications. Does that work? Include your pre-install script. Does that work? Add the subdirectory. Etc, etc. Perhaps this process will lay bare the problem. Best regards, --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

Re: problems running packagemaker from shell script
by Allister Banks 01 Apr '11

01 Apr '11

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

Mysterious .app/Finder corruption?
by Andy O'Meara 01 Apr '11

01 Apr '11

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Hey everyone, I've been trying to get insight into what appears to be an inane bug either within the OS X package installer or the Finder. We use a build script that builds all our .bundles and .apps and then calls package maker via the command line to make our .pkg. Our package creates a new dir in the Applications dir (if it doesn't already exist), and expands the .app into this directory. What's happening is that after the installer runs our package, our .app fails to load our bundle. Yet if I run the .app that the package was given (ie. if I run the app before it gets sucked into the pkg), the app runs fine -- it's as if somehow the .app created by the installer is somehow not right. But it gets stranger... If I *rename* the app via the Finder to anything else (and it says in the same dir), the app then works. When I rename it back to its original name, then it doesn't work again. Stranger yet, if I drag the app to the desktop, then it works. But when I drag it back to its original dir, it doesn't work. Crazy! I can repro all of this on multiple 10.6 machines, and installing on a clean machine seems to have no effect. Rebooting has no effect. If I zip the .app, trash the original .app, and unzip the archive, the new .app still does not work. What could possibly be changing when the bundle name is renamed or moved? I'd submit this as a radar, but I have no way to submit it since the process of moving the app causes the Finder to do stuff behind the scenes to regenerate whatever special sauce it uses to launch the app. Perhaps there's a command line utility that causes something within the Finder to be regenerated? Thanks, Andy _______________________________________________ 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: Option to execute a command?
by Paul Cook 01 Apr '11

01 Apr '11

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