| 1 |
On 09/22/2015 12:15 AM, Ulrich Müller wrote: |
| 2 |
> After commit d4966a381ee4577818bd972946647338046715b1 |
| 3 |
> "match_from_list: restrict =* to match only on version part |
| 4 |
> boundaries" the description of the =* operator in ebuild(5) was |
| 5 |
> no longer accurate. |
| 6 |
> |
| 7 |
> This reverts commit 2b1eceaf79ac667eecdf1ef9585592a235c8d93f. |
| 8 |
> --- |
| 9 |
> man/ebuild.5 | 9 +++------ |
| 10 |
> 1 file changed, 3 insertions(+), 6 deletions(-) |
| 11 |
> |
| 12 |
> diff --git a/man/ebuild.5 b/man/ebuild.5 |
| 13 |
> index 6a27cc5..e60eee1 100644 |
| 14 |
> --- a/man/ebuild.5 |
| 15 |
> +++ b/man/ebuild.5 |
| 16 |
> @@ -96,12 +96,9 @@ Example: |
| 17 |
> .fi |
| 18 |
> .TP |
| 19 |
> .I * |
| 20 |
> -means match any version of the package so long |
| 21 |
> -as the specified string prefix is matched. So with a |
| 22 |
> -version of '2*', we can match '2.1', '2.2', '2.2.1', |
| 23 |
> -etc... and not match version '1.0', '3.0', '4.1', etc... |
| 24 |
> -Beware that, due to the string matching nature, '20' |
| 25 |
> -will also be matched by '2*'. The version part |
| 26 |
> +means match any version of the package so long as the specified base |
| 27 |
> +is matched. So with a version of '2*', we can match '2.1', '2.2', '2.2.1', |
| 28 |
> +etc... and not match version '1.0', '3.0', '4.1', etc... The version part |
| 29 |
> that comes before the '*' must be a valid version in the absence of the '*'. |
| 30 |
> For example, '2' is a valid version and '2.' is not. Therefore, '2*' is |
| 31 |
> allowed and '2.*' is not. |
| 32 |
> |
| 33 |
|
| 34 |
Looks good. |
| 35 |
-- |
| 36 |
Thanks, |
| 37 |
Zac |
Archives