[31565] trunk/base/portmgr/ReleaseProcess

jmpp at macports.org jmpp at macports.org
Tue Nov 27 23:53:05 PST 2007


Revision: 31565
          http://trac.macosforge.org/projects/macports/changeset/31565
Author:   jmpp at macports.org
Date:     2007-11-27 23:53:04 -0800 (Tue, 27 Nov 2007)

Log Message:
-----------
Accept new naming suggestion for our dmgs, starting with the upcoming 1.6.0

Modified Paths:
--------------
    trunk/base/portmgr/ReleaseProcess

Modified: trunk/base/portmgr/ReleaseProcess
===================================================================
--- trunk/base/portmgr/ReleaseProcess	2007-11-28 07:30:40 UTC (rev 31564)
+++ trunk/base/portmgr/ReleaseProcess	2007-11-28 07:53:04 UTC (rev 31565)
@@ -150,8 +150,8 @@
 MacPorts releases (1.x.0), named in a consistent fashion and incorporating the OS version for which it
 was built.
 
- MacPorts-1.6.0-10.4.dmg
- MacPorts-1.6.0-10.5.dmg
+ MacPorts-1.6.0-10.4-Tiger.dmg
+ MacPorts-1.6.0-10.5-Leopard.dmg
 
 To create a disk image, use the MacPorts port. The Portfile will need to be updated to incorporate the
 proper release version and checksums, and the release tarballs will need to be already uploaded to the
@@ -165,8 +165,8 @@
 file in the downloads directory:
 
  cd work
- mv MacPorts-1.6.0.dmg MacPorts-1.6.0-10.5.dmg
- for type in -md5 -sha1 -ripemd160; do openssl dgst $type MacPorts-1.6.0-10.5.dmg; done
+ mv MacPorts-1.6.0.dmg MacPorts-1.6.0-10.5-Leopard.dmg
+ for type in -md5 -sha1 -ripemd160; do openssl dgst $type MacPorts-1.6.0-10.5-Leopard.dmg; done
 
 These new products, along with the new checksums, also have to be posted to the appropriate downloads
 directory of the MacPorts svn repository. Developers are required to validate the generated installer as

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20071127/d616346a/attachment.html


More information about the macports-changes mailing list