1 |
On Thu, 24 Sep 2009 03:39:26 +0200 |
2 |
Maciej Mrozowski <reavertm@××××××.fm> wrote: |
3 |
|
4 |
> And this is the problem (some people may be even unaware of it). |
5 |
> In pre EAPI-2 it was sufficient to do the following in live ebuilds: |
6 |
> |
7 |
> inherit ${some_eclass} ${scm_eclass} |
8 |
> |
9 |
> ${scm_eclass} inherited as last one, would just shadow src_unpack, providing |
10 |
> what we want. |
11 |
|
12 |
Oogh, no. Relying on ordering of the inherit line is never a good idea. If |
13 |
you need to call scm_src_unpack, call scm_src_unpack. |
14 |
|
15 |
> Because SCM bootstrap is either not used at all, or used very rarely, there's |
16 |
> suggestion to: |
17 |
> - either drop it |
18 |
> - or (preferably) to make SCM eclasses export src_prepare only on specific |
19 |
> request |
20 |
> - or to make it easier - to not export it at all - thus making it required for |
21 |
> developer to intentionally invoke ${ECLASS}_src_prepare if bootstrapping is |
22 |
> required. |
23 |
|
24 |
Why not do number 3 but call it ${ECLASS}_bootstrap? If people need it they |
25 |
can call it from src_prepare. |
26 |
|
27 |
|
28 |
-- |
29 |
fonts, Character is what you are in the dark. |
30 |
gcc-porting, |
31 |
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |