| 1 |
On Sunday 25 March 2007, Thomas de Grenier de Latour wrote: |
| 2 |
> My suggestion is only about dropping the substring-match semantics, to |
| 3 |
> replace it with something more restrictive, and that, it's doable for |
| 4 |
> EAPI=0 if decided now. |
| 5 |
|
| 6 |
i'd be on the fence about that ... i feel like some of your examples here of |
| 7 |
where the behavior changes is a bad thing: |
| 8 |
|
| 9 |
> =app-dicts/aspell-en-0.5* |
| 10 |
> --- |
| 11 |
> app-dicts/aspell-en-0.51.0 |
| 12 |
> app-dicts/aspell-en-0.51.1 |
| 13 |
|
| 14 |
you'd have to add more atoms to match 0.51.0, 0.52.1, 0.53.3, etc... |
| 15 |
|
| 16 |
> =app-text/docbook-xsl-stylesheets-1.6* |
| 17 |
> --- |
| 18 |
> app-text/docbook-xsl-stylesheets-1.68.1-r1 |
| 19 |
> --- |
| 20 |
> media-sound/solfege-2.0.5: =app-text/docbook-xsl-stylesheets-1.6*" |
| 21 |
> media-sound/solfege-2.0.6: =app-text/docbook-xsl-stylesheets-1.6*" |
| 22 |
|
| 23 |
same here ... you want 1.6* to match 1.67.0 and 1.68.1 and 1.69.3 ... |
| 24 |
|
| 25 |
considering the pretty subtle problems and headaches this would throw onto the |
| 26 |
heads of developers, i think it'd be saner to leave this logic change for |
| 27 |
EAPI=1 ... |
| 28 |
-mike |
Archives