1 |
On Tuesday 19 June 2012 17:35:00 Jeroen Roovers wrote: |
2 |
> On Tue, 12 Jun 2012 23:02:40 -0400 Mike Frysinger wrote: |
3 |
> > i've noticed a growing trend where people put setup of variables into |
4 |
> > pkg_setup that only matter to src_* funcs presumably so they don't |
5 |
> > have to call the respective src_* func from an inherited eclass. |
6 |
> > unfortunately this adds pointless overhead to binpkgs. can we please |
7 |
> > move away from this practice ? |
8 |
> |
9 |
> Like this? |
10 |
|
11 |
not quite |
12 |
|
13 |
> * ERROR: cat/pkg-version failed (prepare phase): |
14 |
> * python_set_active_version() can be used only in pkg_setup() phase |
15 |
> * |
16 |
> * Call stack: |
17 |
> * ebuild.sh, line 85: Called src_prepare |
18 |
> * environment, line 5885: Called python_set_active_version '2' |
19 |
> * environment, line 5603: Called die |
20 |
> * The specific snippet of code: |
21 |
> * die "${FUNCNAME}() can be used only in pkg_setup() phase"; |
22 |
> * |
23 |
> |
24 |
> Shouldn't that be in src_prepare already, or does python.eclass do |
25 |
> something rather important here while installing a binpkg? |
26 |
|
27 |
Gentoo's python integration is an ugly beast. in this case, i believe it's |
28 |
screwing with your $ROOT which means it has to be in pkg_* (let's quietly |
29 |
ignore what happens if you try to emerge two ebuilds which need conflicting |
30 |
versions of python active). |
31 |
-mike |