1 |
On 26/12/10 16:20, Petteri Räty wrote: |
2 |
> On 12/24/2010 11:19 AM, Justin (jlec) Lecher wrote: |
3 |
>> On 24/12/10 02:18, Arfrever Frehtes Taifersar Arahesis wrote: |
4 |
>>> What do you mean about python.eclass? |
5 |
>>> python.eclass doesn't define python_src_unpack(). |
6 |
>>> |
7 |
>> |
8 |
>> No it doesn't, but calling the default() function in a phase will make |
9 |
>> the default phase be called. And this is implemented in the python.eclass. |
10 |
>> |
11 |
> |
12 |
> default calls the PM implementation, not the eclass implementation. |
13 |
> |
14 |
> From PMS: |
15 |
> |
16 |
> default |
17 |
> |
18 |
> Calls the default_ function for the current phase (see section 10.1.17). |
19 |
> Must not be called if the default_ function does not exist for the |
20 |
> current phase in the current EAPI. Only available in EAPIs listed in |
21 |
> table 12.14. |
22 |
> |
23 |
> 10.1.17: |
24 |
> |
25 |
> DEFAULT-In EAPIs listed in table 10.8 as supporting default_ phase |
26 |
> functions, a function named default_(phase) that behaves as the default |
27 |
> implementation for that EAPI shall be defined when executing any ebuild |
28 |
> phase listed in the table. Ebuilds must not call these functions except |
29 |
> when in the phase in question. |
30 |
> |
31 |
> Regards, |
32 |
> Petteri |
33 |
> |
34 |
|
35 |
Thanks for clarification, Petteri. |
36 |
I only knows this from the python dev guide, so I assumed it to come |
37 |
from python.eclass. |
38 |
|
39 |
justin |