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