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
pgp2QMx8HVhH5.pgp
Description: PGP signature
