| 1 |
On Thu, Aug 03, 2006 at 07:07:35AM +0200, Marius Mauch wrote: |
| 2 |
> Repost from gentoo-portage-dev[1]: |
| 3 |
> |
| 4 |
> Was just brought to my attention that the =* operator doesn't work as I |
| 5 |
> thought, as for example =foo-1.2* matches foo-1.20 as well as foo-1.2.3. |
| 6 |
> This wouldn't be a bug problem if it could be used as a general glob |
| 7 |
> operator like with =foo-1.2.*, |
| 8 |
|
| 9 |
Even if that would be supported, it wouldn't match foo-1.2, unless |
| 10 |
the meaning of * changes. |
| 11 |
|
| 12 |
> but it's use is strictly limited to the |
| 13 |
> above version (can only be used when a version component separator may |
| 14 |
> appear), so atm there is no facility to reliably lock an atom at a |
| 15 |
> specific version component when you have to account for multi-digit |
| 16 |
> components. |
| 17 |
> Now the question is if we want this glob-style behavior or not. From |
| 18 |
> the code comments it seems to be intentional, but I'd suspect that many |
| 19 |
> people share my original assumption and expect it to only match full |
| 20 |
> version components (as that is the much more common use case). Doesn't |
| 21 |
> help that the atom description in ebuild(5) doesn't specify the |
| 22 |
> behavior for this case either, |
| 23 |
> |
| 24 |
> "* means match any version of the package so long as the specified |
| 25 |
> base is matched" |
| 26 |
> |
| 27 |
> can be read both ways. |
| 28 |
> |
| 29 |
> Opinions? |
| 30 |
> |
| 31 |
> Marius |
| 32 |
|
| 33 |
For packages with YYYYMMDD versions, =c/p-2005* can make sense, and |
| 34 |
I have used this in the past. Please continue to allow that, and |
| 35 |
possibly provide an alternative syntax for what you currently expect |
| 36 |
=c/p-v* to do (=c/p-v.* -- if it doesn't require the . -- being a |
| 37 |
possibility). |
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives