1 |
On Tue, 12 Jun 2012 23:02:40 -0400 |
2 |
Mike Frysinger <vapier@g.o> wrote: |
3 |
|
4 |
> i've noticed a growing trend where people put setup of variables into |
5 |
> pkg_setup that only matter to src_* funcs presumably so they don't |
6 |
> have to call the respective src_* func from an inherited eclass. |
7 |
> unfortunately this adds pointless overhead to binpkgs. can we please |
8 |
> move away from this practice ? |
9 |
|
10 |
Like this? |
11 |
|
12 |
* ERROR: cat/pkg-version failed (prepare phase): |
13 |
* python_set_active_version() can be used only in pkg_setup() phase |
14 |
* |
15 |
* Call stack: |
16 |
* ebuild.sh, line 85: Called src_prepare |
17 |
* environment, line 5885: Called python_set_active_version '2' |
18 |
* environment, line 5603: Called die |
19 |
* The specific snippet of code: |
20 |
* die "${FUNCNAME}() can be used only in pkg_setup() phase"; |
21 |
* |
22 |
|
23 |
Shouldn't that be in src_prepare already, or does python.eclass do |
24 |
something rather important here while installing a binpkg? |
25 |
|
26 |
|
27 |
jer |