On Jan 9, 2010, at 03:24, [email protected] wrote:
> Revision: 62487
> http://trac.macports.org/changeset/62487
> Author: [email protected]
> Date: 2010-01-09 01:24:37 -0800 (Sat, 09 Jan 2010)
> Log Message:
> -----------
> py26-pyproj: New port (from existing py25-pyproj)
That's great, but when you do so, please don't also change the port's
whitespace. Whitespace changes should always be made in a separate commit from
functional changes. And if you're going to change one port for a given piece of
software (e.g. py26-pyproj) you should make the same changes to all other ports
for that software (e.g. py25-pyproj) -- having first cleared it with the
maintainer, of course. Different ports for the same piece of software should be
kept as similar as possible. I should be able to "diff -u $(port file
py2{5,6}-pyproj)" and see only the changes necessary to turn the one into the
other, not differences on every line due to whitespace.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
