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