On Sep 26, 2008, at 17:29, Blair Zajac wrote: > Ryan Schmidt wrote: > >> On Sep 26, 2008, at 12:23, [EMAIL PROTECTED] wrote: >> >>> Revision: 40228 >>> http://trac.macports.org/changeset/40228 >>> Author: [EMAIL PROTECTED] >>> Date: 2008-09-26 10:23:04 -0700 (Fri, 26 Sep 2008) >>> Log Message: >>> ----------- >>> New upstream 2.7.2.RC2 release of Scala. >>> >>> Modified Paths: >>> -------------- >>> trunk/dports/lang/scala/Portfile >>> >>> Modified: trunk/dports/lang/scala/Portfile >>> =================================================================== >>> --- trunk/dports/lang/scala/Portfile 2008-09-26 14:40:59 UTC (rev >>> 40227) >>> +++ trunk/dports/lang/scala/Portfile 2008-09-26 17:23:04 UTC (rev >>> 40228) >>> @@ -3,8 +3,7 @@ >>> PortSystem 1.0 >>> >>> name scala >>> -version 2.7.1 >>> -revision 1 >>> +version 2.7.1.99.2.7.2.2 >> >> If one makes use of the epoch variable, then this kind of version >> munging isn't necessary, is it? >> >> Today you would have set the version to "2.7.2.RC2". And at a >> later time >> when 2.7.2 final is released, you would set the version to "2.7.2" >> and >> increase the epoch. Right? > > Right, but I don't plan on increasing the epoch every time though.
You don't need to increase the epoch every time you update the version; only every time you update the version in a way that MacPorts wouldn't otherwise detect -- like when updating from a release candidate to a final version. That's not so bad, is it? And it has the advantage of giving the user the correct version number in "port info" and "port installed" and wherever else. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
