June 2012 - Installer-dev - lists.apple.com

certificate support in Packages?
by Allen Hancock 30 Jun '12

30 Jun '12

Hi I'm looking for more documentation with packagesbuild I see this: http://s.sudre.free.fr/Software/documentation/Packages/en/index.html but don't yet see the syntax for signing a package. My attempts so far have resulted in packages which are signed but with a certificate unknown to other computers. any pointers would be great, thanks! _______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Actions with packagemaker
by vishnu kulkarni 29 Jun '12

29 Jun '12

I have created a pkg using Packagemaker and included the inbuilt requirements for (Hw/Sw) checks for the application. Our requirement is to kill the app and remove the app from applications folder before it gets installed. Initially I was using a script to achieve this goal. However for some reasons it was failing. The reason being the distribution.dist file does not allow external scripts. To over come this I have used Actions within packagemaker. It works great. I have created a Automator workflow and included it in the pkg. Below are my questions 1) Is it a best practice to use Actions instead of Scripts? 2) Are there any minor or major hiccups while using the Action to Remove the App? Please advice. Thanks, Vishnu _______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: permission/owner issues in package maker - osx 10.7
by Per Olofsson 29 Jun '12

29 Jun '12

29 jun 2012 kl. 13:50 skrev Dennis Wolter: > Am 29.06.12 12:30, schrieb Per Olofsson: >> On 28 jun 2012, at 16:18, Dennis Wolter wrote: >> >>> i noticed, there is a "--no-recommend" flag i can use, which is described as follows >>> >>> "If specified, packagemaker will not apply recommended permissions to package contents." >> >> Ah, yes, you definitely want that. I have that in all my scripts and had simply forgotten that it isn't the default. I added it to the StackOverflow post. > > i agree... i think, i definitely want that. already played around with it and the flag can help me solving the issue (though i still have the feeling, the approach of setting permissions on my build system's source folders before packaging is not quite clean). ;) It's not, and it's a bit of a headache. I haven't had a chance to play with pkgbuild/productbuild, but hopefully they don't suffer from the same problems. -- Per Olofsson System Administrator, IT-services, University of Gothenburg _______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: permission/owner issues in package maker - osx 10.7
by Dennis Wolter 29 Jun '12

29 Jun '12

Am 29.06.12 12:30, schrieb Per Olofsson: On 28 jun 2012, at 16:18, Dennis Wolter wrote: hi, thx for your answer, though, i read the stackoverflow thread, too. ;) i'm not sure if that explains the different behavior on my two 10.7 machines which both have exactly the same packagemaker version, the same payload with the same permissions/owner group set before compressing them to archive during package creation process. i noticed, there is a "--no-recommend" flag i can use, which is described as follows "If specified, packagemaker will not apply recommended permissions to package contents." Ah, yes, you definitely want that. I have that in all my scripts and had simply forgotten that it isn't the default. I added it to the StackOverflow post. in the packagemaker man page. what are the recommended permissions and what are the criteria for setting those? they obviously differ under certain circumstances (build environment? destination folder?). I think they're simply taken from the system on the machine it's built on. thx for sharing your thoughts, dennis _______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com i agree... i think, i definitely want that. already played around with it and the flag can help me solving the issue (though i still have the feeling, the approach of setting permissions on my build system's source folders before packaging is not quite clean). ;) yes, see my last mail. i guess i (mostly) understood how the mechanism works.

1 0

Re: permission/owner issues in package maker - osx 10.7
by Dennis Wolter 29 Jun '12

29 Jun '12

hi stephane, thank you for your input. i think i found the reason for this strange behavior: affected system: root:wheel working system: root:admin best, dennis Am 28.06.12 17:15, schrieb Stephane Sudre: On Thu, Jun 28, 2012 at 4:18 PM, Dennis Wolter <dennis.wolter(a)native-instruments.de> wrote: in the packagemaker man page. what are the recommended permissions and what are the criteria for setting those? they obviously differ under certain circumstances (build environment? destination folder?). Ideally, recommendations should be based (for well known locations) on the permissions/ownerships defined in the OS Installation packages. So it may be reasonable to assume that ideally PackageMaker inspects the receipts of the OS Installation packages (such as com.apple.pkg.Essentials) or use the same API as the Disk Utility application when it repairs permissions (which is also based on the receipts AFAIK). This would explain a difference between 2 major OS releases. This would not explain a difference between the exact same OS release (all security updates being installed) on 2 different machines. _______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com i realized that the only difference between the two 10.7 systems was the owner group of my system partition's root directory. i changed the group of the working system's root directory to wheel and was able to reproduce the behavior. the package's IFPkgFlagDefaultLocation is always relative to root, right? so i assume that packagemaker uses just root for determining recommended permissions for the payload. i checked other 10.7 systems, they all come up with wheel group for the root directory. so i guess, my "working" 10.7 just worked as i expected from 10.6 (probably it was upgraded some time from 10.6 and kept the permissions) by accident. strange: DiskUtility's perm repair tool does not complain about the group for root directory, no matter if it is set to admin or wheel.

1 0

Re: permission/owner issues in package maker - osx 10.7
by Per Olofsson 29 Jun '12

29 Jun '12

On 28 jun 2012, at 16:18, Dennis Wolter wrote: > hi, > > thx for your answer, though, i read the stackoverflow thread, too. ;) > i'm not sure if that explains the different behavior on my two 10.7 machines which both have exactly the same packagemaker version, the same payload with the same permissions/owner group set before compressing them to archive during package creation process. > > i noticed, there is a "--no-recommend" flag i can use, which is described as follows > > "If specified, packagemaker will not apply recommended permissions to package contents." Ah, yes, you definitely want that. I have that in all my scripts and had simply forgotten that it isn't the default. I added it to the StackOverflow post. > in the packagemaker man page. what are the recommended permissions and what are the criteria for setting those? they obviously differ under certain circumstances (build environment? destination folder?). I think they're simply taken from the system on the machine it's built on. -- Per Olofsson, IT-service, University of Gothenburg _______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Packages with custom plugins show "Reopen Installer" messsage on MacOS 10.8
by Stephane Sudre 29 Jun '12

29 Jun '12

On Fri, Jun 29, 2012 at 9:23 AM, Vikram Singh <vikram731(a)gmail.com> wrote: > Hi, > > When I am running any package with packagemaker plugins embedded in it, it > shows a message "To Open 'TestApp Installer', Installer must quit and > reopen". When I click on OK, the Installer reopens and then works fine. Any > idea why this might be happening? On first look, it looks like its a bug or > may be I am missing something. I tested this in Mountain Lion Developer > Preview 3. Let's remove the Mountain word from the question because it's still under NDA and let's imagine you tested in on Mac OS X 10.6 or 10.7. Possible explanation for this message: - your plugin binary only includes the i386 architecture (32-bit). Installer.app runs in 64-bit mode. It can not load 32-bit code and execute it. So it has to quit and then force itself to run in 32-bit mode. For the record, you have to build you plugin on Mac OS X 10.6 to be able to add the x86_64 architecture. _______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Packages with custom plugins show "Reopen Installer" messsage on MacOS 10.8
by Vikram Singh 29 Jun '12

29 Jun '12

_______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: How do i include proccessor check in packages?
by Adam Mercer 29 Jun '12

29 Jun '12

On Thu, Jun 28, 2012 at 4:30 PM, vishnu kulkarni <vishnu5876(a)gmail.com> wrote: > I'm trying to include processor check within package while building a > package. It should check for intel processor before getting installed. What > is the best way to achieve this? Something like this I imagine: <http://stackoverflow.com/questions/5782012/packagemaker-differentiate-betwe…> Cheers Adam _______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

How do i include proccessor check in packages?
by vishnu kulkarni 28 Jun '12

28 Jun '12

_______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0