Ok, thanks for clarifying! I won't update the revision in future when simply converting a port to unified format.
Cheers, Tom On 1 February 2012 19:47, Frank Schima <[email protected]> wrote: > You don't need to update the revision when unifying python ports. > > > On Feb 1, 2012, at 10:05 AM, [email protected] wrote: > > Revision 89525 Author [email protected] Date 2012-02-01 09:05:15 -0800 > (Wed, 01 Feb 2012) > > Log Message > > py-aplpy: set revision to 1 (should have done it when updating to unified > port format) > > Modified Paths > > trunk/dports/python/py-aplpy/Portfile > > Diff > > Modified: trunk/dports/python/py-aplpy/Portfile (89524 => 89525) > > --- trunk/dports/python/py-aplpy/Portfile 2012-02-01 17:04:01 UTC (rev > 89524) > +++ trunk/dports/python/py-aplpy/Portfile 2012-02-01 17:05:15 UTC (rev > 89525) > @@ -6,6 +6,7 @@ > > name py-aplpy > version 0.9.6 > +revision 1 > maintainers robitaille stsci.edu:mperrin > > categories-append science > > _______________________________________________ > macports-changes mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-changes > > _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
