Bugs, Certificates, PackageMaker and Installer
Bugs, Certificates, PackageMaker and Installer
- Subject: Bugs, Certificates, PackageMaker and Installer
- From: Iceberg-Dev <email@hidden>
- Date: Thu, 18 Feb 2010 23:33:34 +0100
While playing with PackageMaker to try to figure out where the hash-
sha256 value was coming from in a distribution script, I think I
bumped into numerous bugs in PackageMaker.
Bug #1: If you create a flat distribution with one of the packages
being at the same level of the distribution, the relative path of the
package is incorrect in the Distribution.
It will set the relative path to file:./../MyPackage.pkg.
This is correct for a bundle distribution. Not for a flat
distribution apparently. I'm not the one saying that. Installer.app is.
Bug #2: If you put the package one level higher, Installer.app will
then complain that the hash-sha256 key-value is missing for the package.
Bug #3: If you try to sign this distribution, the related package
will be signed too (which is OK AFAIK). But Installer.app will fail
saying the package can not be trusted or something like that.
Bug #4: The error message for Bug #3 is totally unclear and put the
blame on the author of the package while it's not the guy's fault but
either PackageMaker or Installer.app fault.
Bug #5: If you don't sign the distribution, the installation will
fail with Installer.app complaining that there is no software to
install.
All of this with the latest OS X version and the latest Dev Tools.
I will definitely file numerous bug reports in Radar so that this can
be tracked.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden