commit:     f3a7a9aaed8a3affc56cf3cbd23f18d8a01120b1
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Tue Sep 22 07:15:12 2015 +0000
Commit:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
CommitDate: Tue Sep 22 16:38:41 2015 +0000
URL:        https://gitweb.gentoo.org/proj/portage.git/commit/?id=f3a7a9aa

man/ebuild.5: Update description of =* operator.

After commit d4966a381ee4577818bd972946647338046715b1
"match_from_list: restrict =* to match only on version part
boundaries" the description of the =* operator in ebuild(5) was
no longer accurate.

This reverts commit 2b1eceaf79ac667eecdf1ef9585592a235c8d93f.

 man/ebuild.5 | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/man/ebuild.5 b/man/ebuild.5
index 6a27cc5..e60eee1 100644
--- a/man/ebuild.5
+++ b/man/ebuild.5
@@ -96,12 +96,9 @@ Example:
 .fi
 .TP
 .I *
-means match any version of the package so long
-as the specified string prefix is matched. So with a
-version of '2*', we can match '2.1', '2.2', '2.2.1',
-etc... and not match version '1.0', '3.0', '4.1', etc...
-Beware that, due to the string matching nature, '20'
-will also be matched by '2*'. The version part
+means match any version of the package so long as the specified base
+is matched.  So with a version of '2*', we can match '2.1', '2.2', '2.2.1',
+etc... and not match version '1.0', '3.0', '4.1', etc... The version part
 that comes before the '*' must be a valid version in the absence of the '*'.
 For example, '2' is a valid version and '2.' is not. Therefore, '2*' is
 allowed and '2.*' is not.

Reply via email to