[55528] trunk/dports/python

[Ryan Schmidt]

On Aug 12, 2009, at 17:57, singingwolfboy at macports.org wrote:

> Revision: 55528
>           http://trac.macports.org/changeset/55528
> Author:   singingwolfboy at macports.org
> Date:     2009-08-12 15:57:28 -0700 (Wed, 12 Aug 2009)
> Log Message:
> -----------
> added portfile for py26-duplicity, based on duplicity portfile
>
> Added Paths:
> -----------
>     trunk/dports/python/py26-duplicity/
>     trunk/dports/python/py26-duplicity/Portfile


For future reference, when you create a new port based on another  
port, it's usually best to "svn cp" the old port directory to the new  
one and then make changes. That way it's easy to see what changes  
were made to get from the one to the other, and it makes "svn log"  
and "svn blame" work on the new port so that you can still see the  
reasons why the rest of the lines in the portfile were written the  
way they were.

You also should set up your Subversion autoprops so that  
svn:keywords=Id and svn:eol-style=native are automatically added to  
Portfiles. These properties are missing on this Portfile.

However, in this case, I don't believe you should have created a new  
port py26-duplicity. The old port was not py25-duplicity but  
duplicity, and was not in the python category but the sysutils  
category. Ports in the python category are Python modules and should  
ideally exist for multiple Python versions. But Duplicity is just a  
utility that happened to use Python. If your goal was to get  
Duplicity to use Python 2.6, then I think the correct course of  
action is to update the duplicity port, and delete py26-duplicity again.