[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev] portageq in global scope == die
From:       Brian Harring <ferringb () gentoo ! org>
Date:       2005-09-28 4:58:45
Message-ID: 20050928045845.GJ30337 () nightcrawler
[Download RAW message or body]

Hola all.

The short version of it is that there is no good reason to be using 
has_version/portageq in the global scope; it's slow, it's not allowed, 
and any attempts to change metadata via it screw up the build plan.  

It's really a no go... so next version of portage will trigger an 
immediate die whenever portageq is called in the global scope.  Won't 
be possible to pull it off globally, in other words.

The logic for this comes down to the reasons raised above; mainly, 
it's a snake in the grass for bugs.

Those affected by it I've filed bugs against (check your email iow); 
in the meantime, giving people a heads up on this one.

~harring

[Attachment #3 (application/pgp-signature)]
-- 
gentoo-dev@gentoo.org mailing list


[prev in list] [next in list] [prev in thread] [next in thread]