On Tuesday 23 September 2008 22:44:35 Alexis Ballier wrote:
> > > False. If for instance coolfeature was made optional in >=pv you
> > > can use logic like:
> > >
> > > if has_version '>=cat/foo-pv' && ! has_version
> > > 'cat/foo[coolfeature]'; then ewarn '...'
> > > fi
> >
> > I think this should cover all the current functionality with
> > built_with_use.
>
> This is just an ugly hack. Think about a package that has coolfeature
> useflag removed and enabled by default for a couple of releases because
> it wouldn't build without it and once upstream sorted out everything
> the useflag is coming back. Missing useflags that are assumed to be
> enabled have nothing to do with the package version being greater than
> a given number.

If it is needed that often we should add support for stating the state of the 
use flag in dependencies. With the currently planned eapi 2 you get 
dependencies such as:

DEPEND="|| ( >=cat/foo-pv[coolfeature] <cat-foo-pv )"

too. Doing the same with has_version is only consistent with that. If we add 
support for it in dependency syntax it will work with has_version too...

-- 
Bo Andresen