1 |
Hi, |
2 |
|
3 |
thx for the quick fix! I am not that firm with eclasses. |
4 |
But i will start/continue moving ebuilds to eapi2. |
5 |
As far as i have noticed it is not that hard to port ebuilds to eapi2 for most |
6 |
packages. But please make sure to test every package at least once.;) |
7 |
|
8 |
Am Friday 19 February 2010 15:42:42 schrieb Chris Bandy: |
9 |
> Ladislav Laska wrote: |
10 |
> > Sure we can, in fact, it was like this until recently. |
11 |
> > |
12 |
> > Well, I've grepped ebuilds and found 43 with EAPI=0/1 and more with no |
13 |
> > EAPI set. That's a lot of packages and since I don't have time to fix |
14 |
> > all of them, I'll commit workaround. Feel free to remove it when all |
15 |
> > packages are fixed. |
16 |
> > |
17 |
> > Regards Ladislav Laska |
18 |
> > S pozdravem Ladislav Laska |
19 |
> > --- |
20 |
> > xmpp/jabber: ladislav.laska@××××××.cz |
21 |
> |
22 |
> Thank you very much. If porting from EAPI=1 to 2 is as simple as your |
23 |
> commit for my two packages, I'd be happy to test some others and submit |
24 |
> patches. |
25 |
> |
26 |
> Does it make sense to emit a QA/warning when you find PATCHES in EAPI=0|1 ? |
27 |
> |
28 |
> -- Chris |
29 |
|
30 |
|
31 |
greetings, |
32 |
Roman |
33 |
|
34 |
-- |
35 |
Love is being stupid together. |
36 |
-- Paul Valery |