Re: [gentoo-portage-dev] Atom matching behavior

[Mike Frysinger]

On Sunday 25 March 2007, Thomas de Grenier de Latour wrote:
> On 2007/03/25, Mike Frysinger <vapier@g.o> wrote:
> > > =app-dicts/aspell-en-0.5*
> > > ---
> > > app-dicts/aspell-en-0.51.0
> > > app-dicts/aspell-en-0.51.1
> >
> > you'd have to add more atoms to match 0.51.0, 0.52.1, 0.53.3, etc...
>
> Yes and no...
>
> On one hand, only 0.51.{0,1} exist atm, so a dep on =0.51* would be
> enough.
>
> Now, i understand you want to anticipate some hypothetical future
> versions.

it isnt hypothetical, look at the history of aspell ... it had versions that 
matched my example

app-text/docbook-xsl-stylesheets have examples right now that match what i'm 
talking about

> But if you go that road, then i don't buy the argument:
>  - there are numerous ~foo/bar-1.1 deps around, which doesn't take
> hypothetical future 1.1.1 compatible version into account.  How is
> this "0.5x" particular case different, why would it be more a problem
> than the usual case?
>  - there are numerous =0.1* deps around written with only 0.1.x in
> mind...  If hypothetical future versions really matter, then what about
> an incompatible 0.10?  Imho, taking them into account pleads for
> dropping the substring match semantics, rather than keeping it.

it works now because package maintainers tend to follow one course or the 
other ... in other words, people who do x.y.z releases do not generally do 
x.yz.w releases and vice versa

but each has obvious pros and cons that arent debatable, they're fact ... so 
if we're gonna get screwed one way or the other, best to keep old behavior 
for EAPI=0 and leave the logical (from the point of view of the pm parsing 
the version) switch for EAPI=1 ...
-mike