On Nov 17, 2012, at 12:31, Sean Farley <[email protected]> wrote:
> This is another example of the internal macports comparison code not > recognizing release candidates. Is there any reason to not fix that > (backwards compatibility?)? How do you propose to fix it? I assume we're talking about making changes to the vercmp procedure, but what changes exactly? _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
