On Nov 17, 2012, at 14:35, Sean Farley <[email protected]> wrote:
> On Sat, Nov 17, 2012 at 2:18 PM, Ryan Schmidt <[email protected]> wrote: >> >> 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? > > Basically, I was thinking of following the algorithm described for > parse_version: > > http://packages.python.org/distribute/pkg_resources.html#parsing-utilities > > This would fix so many wrong version comparisons that are due to > '1.0-rc', '3.0-1', etc. ... but I usually try to avoid the deep > internals of macports since it's all in tcl :-P There certainly are a lot of rules described there. I don't know what implication implementing some or all of those rules would have on our thousands of existing ports and the different version numbering schemes their developers use. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
