Short answer: Sorry, but yes. Signed flat distribution packages (aka mpkgs) can only contain flat payload packages. This is because the way we sign stuff only works for a single archive file (xar format), aka flat package. So yeah, you gotta flatten all your payloads, and if you have preflights and postflights, they'll require reworking. The good news is, your stuff will all be signed, and harder to damage in transit. On May 15, 2012, at 5:56 PM, Monte Benaresh wrote:

We currently use Iceberg to build .mpkg bundles from our .pkg bundles. However, it seems that in order to use Developer ID to sign our installer packages, we need to start using PM or Packages to create flat distributions that we can sign with productsign.

So, we would like to be able to create new flat distribution projects which import our existing .pkg bundles. I tried this in PM, and it seems that once you include a .pkg, it will produce .mpkg bundles rather than flat distributions. As far as I can see, Packages cannot import .pkg bundles at all.

Are my conclusions correct? In order to sign with Developer ID, will we be forced to re-create all of our package and metapackage projects with one of the newer tools?

Thanks very much for any advice.

Monte Benaresh PACE Anti-Piracy

_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/bc%40apple.com

This email sent to bc@apple.com

_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@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@lists.apple.com