Re: [gentoo-dev] portage-2.0.51_pre10: QA Notice Messages

[Paul de Vrieze]

On Friday 11 June 2004 21:01, Ned Ludd wrote:
> On Fri, 2004-06-11 at 14:17, Paul de Vrieze wrote:
> > > IUSE isnt defined when portage hits that (it is defined later on) so
> > > you get the warning message ... portage needs a way to handle
> > > conditional inherits, so you cant really say the eclass/ebuild is
> > > broken
> >
> > No it doesn't, those eclasses / ebuilds need to be written in such that
> > there is no need for a conditional use of them.
>
> Well in the case if the flag-o-matic one, it's going to yap at us no
> matter what. The IUSE is defined unconditionally, first properly
> IUSE=debug then later on IUSE="$IUSE debug"
>
> The only way I've found to get portage to shutup and behave half sane is
> to hack the .ebuild.sh
>
> -if ! hasq "${u}" ${IUSE} && ! hasq "${u}" ${PORTAGE_ARCHLIST} selinux;
> then
> +if ! hasq "${u}" ${IUSE} && ! hasq "${u}" ${PORTAGE_ARCHLIST} selinux
> debug; then
>
> This type of hack will probably have to be used on *all* IUSE/USE flags
> called from any .eclass as far as I can tell if you want to keep your
> sanity.

portage could also be hacked up in such a way that it does the right thing 
(tm) with eclass IUSE variables. I just don't like conditional eclass 
includes.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@g.o
Homepage: http://www.devrieze.net