1 |
Sure we can, in fact, it was like this until recently. |
2 |
|
3 |
Well, I've grepped ebuilds and found 43 with EAPI=0/1 and more with no |
4 |
EAPI set. That's a lot of packages and since I don't have time to fix |
5 |
all of them, I'll commit workaround. Feel free to remove it when all |
6 |
packages are fixed. |
7 |
|
8 |
Regards Ladislav Laska |
9 |
S pozdravem Ladislav Laska |
10 |
--- |
11 |
xmpp/jabber: ladislav.laska@××××××.cz |
12 |
|
13 |
|
14 |
|
15 |
On Fri, Feb 19, 2010 at 2:34 PM, Ben de Groot <yngwin@g.o> wrote: |
16 |
> On 19 February 2010 13:14, Ladislav Laska <ladislav.laska@×××××.com> wrote: |
17 |
>> Removing this, only src_prepare in ebuild or in base.eclass |
18 |
>> can be invoked, both of them will do just fine. |
19 |
>> |
20 |
>> Unfortunately, src_prepare is eapi=2 thing, so we have to migrate all |
21 |
>> packages with patches to eapi 2, but this should not be a problem, |
22 |
>> since i've seen someone is already doing that. |
23 |
> |
24 |
> If you don't want to port all ebuilds to eapi-2, then you could use a |
25 |
> workaround and call kde_src_prepare in kde_src_unpack() when eapi is 0 |
26 |
> or 1. Some eclasses in the portage tree use this, see for example |
27 |
> git.eclass. |
28 |
> |
29 |
> Cheers, |
30 |
> -- |
31 |
> Ben de Groot |
32 |
> Gentoo Linux developer (qt, media, lxde, desktop-misc) |
33 |
> ______________________________________________________ |
34 |
> |
35 |
> |