| 1 |
Repost from gentoo-portage-dev[1]: |
| 2 |
|
| 3 |
Was just brought to my attention that the =* operator doesn't work as I |
| 4 |
thought, as for example =foo-1.2* matches foo-1.20 as well as foo-1.2.3. |
| 5 |
This wouldn't be a bug problem if it could be used as a general glob |
| 6 |
operator like with =foo-1.2.*, but it's use is strictly limited to the |
| 7 |
above version (can only be used when a version component separator may |
| 8 |
appear), so atm there is no facility to reliably lock an atom at a |
| 9 |
specific version component when you have to account for multi-digit |
| 10 |
components. |
| 11 |
Now the question is if we want this glob-style behavior or not. From |
| 12 |
the code comments it seems to be intentional, but I'd suspect that many |
| 13 |
people share my original assumption and expect it to only match full |
| 14 |
version components (as that is the much more common use case). Doesn't |
| 15 |
help that the atom description in ebuild(5) doesn't specify the |
| 16 |
behavior for this case either, |
| 17 |
|
| 18 |
"* means match any version of the package so long as the specified |
| 19 |
base is matched" |
| 20 |
|
| 21 |
can be read both ways. |
| 22 |
|
| 23 |
Opinions? |
| 24 |
|
| 25 |
Marius |
| 26 |
|
| 27 |
[1] |
| 28 |
http://thread.gmane.org/gmane.linux.gentoo.portage.devel/2231/focus=2231 |
| 29 |
|
| 30 |
-- |
| 31 |
Public Key at http://www.genone.de/info/gpg-key.pub |
| 32 |
|
| 33 |
In the beginning, there was nothing. And God said, 'Let there be |
| 34 |
Light.' And there was still nothing, but you could see a bit better. |
Archives