while writing some code in qpkg for testing version atoms, i noticed portage gets this scenario wrong: $ python -c 'import portage; print portage.dep.match_from_list("=c/p-1-r1*", ["c/p-1_alpha1"])' ['c/p-1_alpha1'] that should of course be [] you can see this with a simple ebuild too: $ cd /usr/portage/sys-libs/ldb $ mv ldb-1.1.12.ebuild ldb-1_alpha1.ebuild $ rm ldb-1.* $ emerge =ldb-1-r1* -qpv --nodeps [ebuild N ] sys-libs/ldb-1_alpha1 USE="-doc" simple update to the test suite to catch this (the pym/portage/tests/dep/test_match_from_list.py file): + ("=cat/pkg-1-r1*", ["cat/pkg-1_alpha1"], []), tested 2.2.0_alpha170 and latest git tree -- both fail
another example: c/a-1 != =c/a-1.0* imo, that should match, but portage doesn't think so currently
(In reply to SpanKY from comment #1) > another example: > c/a-1 != =c/a-1.0* > > imo, that should match, but portage doesn't think so currently Well, PMS specifies "string prefix comparison" for this case: http://dev.gentoo.org/~ulm/pms/5/pms.html#x1-840008.2.6.1
(In reply to SpanKY from comment #0) > while writing some code in qpkg for testing version atoms, i noticed portage > gets this scenario wrong: > $ python -c 'import portage; > print portage.dep.match_from_list("=c/p-1-r1*", ["c/p-1_alpha1"])' > ['c/p-1_alpha1'] > that should of course be [] This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=889e19d27ac978dbbc9699bac152657675569ebd
This is fixed in 2.1.12.4 and 2.2.0_alpha179. For comment #1, we might consider revising PMS?
