[76912] trunk/dports/devel/bzr-svn
Ryan Schmidt
ryandesign at macports.org
Sat Mar 12 14:14:19 PST 2011
On Mar 12, 2011, at 12:06, raimue at macports.org wrote:
> Revision: 76912
> http://trac.macports.org/changeset/76912
> Author: raimue at macports.org
> Date: 2011-03-12 10:06:25 -0800 (Sat, 12 Mar 2011)
> Log Message:
> -----------
> devel/bzr-svn: Switch to python27, add patch for bzrlib 2.3.0
>
> Modified Paths:
> --------------
> trunk/dports/devel/bzr-svn/Portfile
>
> Added Paths:
> -----------
> trunk/dports/devel/bzr-svn/files/
> trunk/dports/devel/bzr-svn/files/patch-bzr-2.3.0.diff
>
> Modified: trunk/dports/devel/bzr-svn/Portfile
> ===================================================================
> --- trunk/dports/devel/bzr-svn/Portfile 2011-03-12 18:05:12 UTC (rev 76911)
> +++ trunk/dports/devel/bzr-svn/Portfile 2011-03-12 18:06:25 UTC (rev 76912)
> @@ -1,11 +1,12 @@
> # $Id$
>
> PortSystem 1.0
> -PortGroup python26 1.0
> +PortGroup python27 1.0
>
> name bzr-svn
> +version 1.0.4
> +revision 1
> epoch 1
> -version 1.0.4
> set branch [join [lrange [split ${version} .] 0 1] .]
> categories devel python
> platforms darwin
We should probably continue to try to keep the epoch line *above* the version line, since it has a *higher* precedence for MacPorts than the version or revision. Placing it below the version line gives it the impression of having a lower precedence and inviting a future contributor to believe the epoch line can or should be removed when increasing the version, which is not correct.
More information about the macports-dev
mailing list