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