[95877] trunk/base/portmgr/ReleaseProcess
jmr at macports.org
jmr at macports.org
Wed Jul 25 10:31:38 PDT 2012
Revision: 95877
https://trac.macports.org/changeset/95877
Author: jmr at macports.org
Date: 2012-07-25 10:31:38 -0700 (Wed, 25 Jul 2012)
Log Message:
-----------
update ReleaseProcess
Modified Paths:
--------------
trunk/base/portmgr/ReleaseProcess
Modified: trunk/base/portmgr/ReleaseProcess
===================================================================
--- trunk/base/portmgr/ReleaseProcess 2012-07-25 17:30:03 UTC (rev 95876)
+++ trunk/base/portmgr/ReleaseProcess 2012-07-25 17:31:38 UTC (rev 95877)
@@ -157,11 +157,16 @@
sudo port -d pkg MacPorts
sudo port -d dmg MacPorts
-Name the pkg/dmg appropriately, and generate checksums, which will need to be added to the existing checksums
+Name each pkg/dmg appropriately, and then sign the pkgs with a Developer ID (make sure to use the
+Installer certificate, not the Application one):
+
+ cd work
+ mv MacPorts-2.0.0.pkg unsigned/MacPorts-2.0.0-10.7-Lion.pkg
+ productsign --sign "Developer ID Installer: John Doe" unsigned/MacPorts-2.0.0-10.7-Lion.pkg MacPorts-2.0.0-10.7-Lion.pkg
+
+After signing, generate checksums, which will need to be added to the existing checksums
file in the downloads directory:
- cd work
- mv MacPorts-2.0.0.pkg MacPorts-2.0.0-10.6-SnowLeopard.pkg
for pkg in MacPorts-2.0.0-*.{pkg,dmg}; do for type in -md5 -sha1 -ripemd160 -sha256; do openssl dgst $type $pkg; done >> MacPorts-2.0.0.chk.txt; done
These new products, along with the new checksums, also have to be posted to the appropriate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20120725/ba460949/attachment.html>
More information about the macports-changes
mailing list