Re: [gentoo-portage-dev] [PATCH] man/ebuild.5: Update description of =* operator.

[Brian Dolbec]

On Tue, 22 Sep 2015 07:19:35 -0700
Zac Medico <zmedico@g.o> wrote:

> On 09/22/2015 12:15 AM, Ulrich Müller wrote:
> > 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.
> >
>
> Looks good.

yes, looks good other than the flak that has already started in
#gentoo-portage last night over the change...

It seems zero_chaos relied on the old behaviour, and at least one other
dev was upset over it.

almost sounded like it was going to be a pitch-forks, torches
mob was going to form ;)

But, I wonder if the change had a bug side effect...causing him the
grief
-- 
Brian Dolbec <dolsen>