[47752] trunk/dports/python/py26-macholib/Portfile
Jordan K. Hubbard
jkh at apple.com
Thu Mar 5 11:33:21 PST 2009
On Mar 5, 2009, at 1:18 AM, Ryan Schmidt wrote:
> This change is bad because a port must never pull from a Subversion
> trunk. Doing so means that users installing the port at different
> times get different versions of the software, as upstream continues
> their development. Please use a distfile if possible, as the port
> used to do before your change. If that's not possible and accessing
> Subversion is the only option, then you should use a tag URL if
> possible. I see upstream has not created a tag for 1.2.1. They don't
> have a tag for 1.2 either. 1.2 seems to be the version currently
> being developed on trunk. So I question your choice of version
> number in this update. Without a tag, you must at least pin the
> checkout to a particular revision. In this case, was r24 the change
> you were interested in? Then use "svn.tag 24". Or perhaps a better
> option would be to leave the port at version 1.1 and just apply the
> minimum patches necessary to make it work properly.
I believe Subversion also lets you check out by date. Therefore, if
you (the portfile author) has confirmed that everything is just peachy
at 3:02PM, March 3rd 2009, then just checkout with --revision set to
that date. You don't have to go looking for a specific tag.
- Jordan
More information about the macports-dev
mailing list