Re: productsign [update]
Re: productsign [update]
- Subject: Re: productsign [update]
- From: Michael Babin <email@hidden>
- Date: Wed, 01 Aug 2012 13:44:29 -0500
On Aug 1, 2012, at 8:54 AM, Michael Babin wrote: Relative paths work fine, in my experience.
You do have to specify an output-product-path that is not the same as the input-product-path (as documented in the man page).
assume I am directory PKG
Then productsign --sign "cert" a.pkg b.pkg
does not work even though
/PKG/a.pkg
is different from
/PKG/b.pkg
Further, when an error in path(s) is encountered to only display the usage information is lame.
If the error is in the cert then it tells you that.
But like anything, now that I know how to use i, it is easy … LOL
cd ~/Desktop/
ls -al | grep pkg -rw-r--r--@ 1 mbabin mbabin 6139904 Aug 1 09:48 a.pkg
productsign --sign "Developer ID Installer: <company name>" a.pkg b.pkg productsign: using timestamp authority for signature productsign: signing product with identity "Developer ID Installer: <company name>" from keychain /Users/mbabin/Library/Keychains/login.keychain productsign: adding certificate "Developer ID Certification Authority" productsign: adding certificate "Apple Root CA" productsign: Wrote signed product archive to b.pkg
ls -al | grep pkg -rw-r--r--@ 1 mbabin mbabin 6139904 Aug 1 09:48 a.pkg -rw-r--r-- 1 mbabin mbabin 6152809 Aug 1 13:40 b.pkg
How does this differ from your steps? Other than using a certificate with a different common name, of course.
|
_______________________________________________
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