Sure we can, in fact, it was like this until recently.
Well, I've grepped ebuilds and found 43 with EAPI=0/1 and more with no
EAPI set. That's a lot of packages and since I don't have time to fix
all of them, I'll commit workaround. Feel free to remove it when all
packages are fixed.
Regards Ladislav Laska
S pozdravem Ladislav Laska
On Fri, Feb 19, 2010 at 2:34 PM, Ben de Groot <firstname.lastname@example.org> wrote:
> On 19 February 2010 13:14, Ladislav Laska <ladislav.laska@...> wrote:
>> Removing this, only src_prepare in ebuild or in base.eclass
>> can be invoked, both of them will do just fine.
>> Unfortunately, src_prepare is eapi=2 thing, so we have to migrate all
>> packages with patches to eapi 2, but this should not be a problem,
>> since i've seen someone is already doing that.
> If you don't want to port all ebuilds to eapi-2, then you could use a
> workaround and call kde_src_prepare in kde_src_unpack() when eapi is 0
> or 1. Some eclasses in the portage tree use this, see for example
> Ben de Groot
> Gentoo Linux developer (qt, media, lxde, desktop-misc)