1 |
Hola all. |
2 |
|
3 |
The short version of it is that there is no good reason to be using |
4 |
has_version/portageq in the global scope; it's slow, it's not allowed, |
5 |
and any attempts to change metadata via it screw up the build plan. |
6 |
|
7 |
It's really a no go... so next version of portage will trigger an |
8 |
immediate die whenever portageq is called in the global scope. Won't |
9 |
be possible to pull it off globally, in other words. |
10 |
|
11 |
The logic for this comes down to the reasons raised above; mainly, |
12 |
it's a snake in the grass for bugs. |
13 |
|
14 |
Those affected by it I've filed bugs against (check your email iow); |
15 |
in the meantime, giving people a heads up on this one. |
16 |
|
17 |
~harring |