diff options
author | Zac Medico <zmedico@gentoo.org> | 2010-01-04 21:30:22 +0000 |
---|---|---|
committer | Zac Medico <zmedico@gentoo.org> | 2010-01-04 21:30:22 +0000 |
commit | 157e2065c3327e5cab22af9c74e9a46b47d18f29 (patch) | |
tree | f6cd4da2e6d87154c77ce58247950da48fd69969 /pym/portage/tests/versions | |
parent | 9f39407d845820b8e864e1a0d03b8102936f5aa0 (diff) | |
download | portage-157e2065c3327e5cab22af9c74e9a46b47d18f29.tar.gz portage-157e2065c3327e5cab22af9c74e9a46b47d18f29.tar.bz2 portage-157e2065c3327e5cab22af9c74e9a46b47d18f29.zip |
Revert r15161 so 12.2.5 is greater than 12.2b once again. Depending on how you
look at, it may seem counter-intuitive. However, if you really think about it,
it seems like it's probably safe to assume that 12.2.5 > 12.2b is the behavior
that is intended by anyone who would use versions such as these.
svn path=/main/trunk/; revision=15166
Diffstat (limited to 'pym/portage/tests/versions')
-rw-r--r-- | pym/portage/tests/versions/test_vercmp.py | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/pym/portage/tests/versions/test_vercmp.py b/pym/portage/tests/versions/test_vercmp.py index 9de3344ce..eb2ba3eb0 100644 --- a/pym/portage/tests/versions/test_vercmp.py +++ b/pym/portage/tests/versions/test_vercmp.py @@ -18,11 +18,11 @@ class VerCmpTestCase(TestCase): ("cvs.9999", "9999"), ("999999999999999999999999999999", "999999999999999999999999999998"), ("1.0.0", "1.0"), - ("1.0b", "1.0.0"), + ("1.0.0", "1.0b"), ("1b", "1"), ("1b_p1", "1_p1"), ("1.1b", "1.1"), - ("12.2b", "12.2.5"), + ("12.2.5", "12.2b"), ] for test in tests: self.failIf( vercmp( test[0], test[1] ) <= 0, msg="%s < %s? Wrong!" % (test[0],test[1]) ) @@ -41,11 +41,11 @@ class VerCmpTestCase(TestCase): ("1.0-r0", "1.0-r1"), ("1.0", "1.0-r1"), ("1.0", "1.0.0"), - ("1.0.0", "1.0b"), + ("1.0b", "1.0.0"), ("1_p1", "1b_p1"), ("1", "1b"), ("1.1", "1.1b"), - ("12.2.5", "12.2b"), + ("12.2b", "12.2.5"), ] for test in tests: self.failIf( vercmp( test[0], test[1]) >= 0, msg="%s > %s? Wrong!" % (test[0],test[1])) |