| 1 |
On 2007/03/25, Mike Frysinger <vapier@g.o> wrote: |
| 2 |
|
| 3 |
> > =app-dicts/aspell-en-0.5* |
| 4 |
> > --- |
| 5 |
> > app-dicts/aspell-en-0.51.0 |
| 6 |
> > app-dicts/aspell-en-0.51.1 |
| 7 |
> |
| 8 |
> you'd have to add more atoms to match 0.51.0, 0.52.1, 0.53.3, etc... |
| 9 |
|
| 10 |
Yes and no... |
| 11 |
|
| 12 |
On one hand, only 0.51.{0,1} exist atm, so a dep on =0.51* would be |
| 13 |
enough. |
| 14 |
|
| 15 |
Now, i understand you want to anticipate some hypothetical future |
| 16 |
versions. But if you go that road, then i don't buy the argument: |
| 17 |
- there are numerous ~foo/bar-1.1 deps around, which doesn't take |
| 18 |
hypothetical future 1.1.1 compatible version into account. How is |
| 19 |
this "0.5x" particular case different, why would it be more a problem |
| 20 |
than the usual case? |
| 21 |
- there are numerous =0.1* deps around written with only 0.1.x in |
| 22 |
mind... If hypothetical future versions really matter, then what about |
| 23 |
an incompatible 0.10? Imho, taking them into account pleads for |
| 24 |
dropping the substring match semantics, rather than keeping it. |
| 25 |
|
| 26 |
> considering the pretty subtle problems and headaches this would throw |
| 27 |
> onto the heads of developers, i think it'd be saner to leave this |
| 28 |
> logic change for EAPI=1 ... |
| 29 |
|
| 30 |
Ok, fair enough. |
| 31 |
|
| 32 |
-- |
| 33 |
TGL. |
| 34 |
-- |
| 35 |
gentoo-portage-dev@g.o mailing list |
Archives