[74831] trunk/dports/python

Ryan Schmidt ryandesign at macports.org
Tue Jan 4 17:45:58 PST 2011

On Jan 3, 2011, at 08:52, lightnin at macports.org wrote:

> Revision: 74831
>          http://trac.macports.org/changeset/74831
> Author:   lightnin at macports.org
> Date:     2011-01-03 06:52:05 -0800 (Mon, 03 Jan 2011)
> Log Message:
> -----------
> Added pyrex port for Python 2.7
> Added Paths:
> -----------
>    trunk/dports/python/py27-pyrex/
>    trunk/dports/python/py27-pyrex/Portfile
> Added: trunk/dports/python/py27-pyrex/Portfile
> ===================================================================
> --- trunk/dports/python/py27-pyrex/Portfile	                        (rev 0)
> +++ trunk/dports/python/py27-pyrex/Portfile	2011-01-03 14:52:05 UTC (rev 74831)

When you create a new port that differs very minimally from an existing port, such as especially when creating a port of a python module that already has a port for a different version of python, it's best to "svn cp" the existing port and make changes, rather than committing the port to the repository as if it were a completely new file, as you did here. Using "svn cp" will preserve the history, making commands like "svn blame" and "svn log" work for this port and be useful. This will also preserve any Subversion properties that were on the file, for example the svn:keywords and svn:eol-style keywords we want all portfiles to carry. You should also set up auto-props in your Subversion config file to automatically add those properties to new portfiles. See the guide for more info.

More information about the macports-dev mailing list