|author||Zac Medico <firstname.lastname@example.org>||2010-08-06 17:45:45 -0700|
|committer||Zac Medico <email@example.com>||2010-08-06 17:45:45 -0700|
|parent||Use ResolverPlayground for it's config instance, so that we don't (diff)|
Bug #331413 - Clarify the behavior of the =$CATEGORY/$PN-$VERSION* atom
operator some more. Thanks to Dennis Schridde <firstname.lastname@example.org>.
1 files changed, 6 insertions, 3 deletions
diff --git a/man/ebuild.5 b/man/ebuild.5
index e3936653..94f49d70 100644
@@ -286,9 +286,12 @@ and explicitly disallow them from being temporarily installed
simultaneously during a series of upgrades. This syntax is supported
beginning with \fBEAPI 2\fR.
-\fI*\fR 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
+\fI*\fR 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
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.