On Tue, Jul 23, 2013 at 11:56 AM, Frank Schima <[email protected]> wrote:
> The revision needs to be reset to 0 when increasing the revision. This was in a testing repository prior to being committed to the main MacPorts repo. We found a problem with revision 0, hence having revision 1. If this was committed as revision 0, then folk who installed it from the testing repository wouldn't have got the update once it was moved into the main MacPorts repo. Cheers Adam _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
