1 |
Feel free to do so, it will usually be matter of rewriting 1 to 2, but |
2 |
you need to check for some nonstandard behavior, which could be |
3 |
broken. |
4 |
|
5 |
Yes, it does make sense. I've commited patch to do so. |
6 |
|
7 |
I'll probably try to rebuild my kde too, in order to check for similar issues. |
8 |
|
9 |
Regards Ladislav Laska |
10 |
S pozdravem Ladislav Laska |
11 |
--- |
12 |
xmpp/jabber: ladislav.laska@××××××.cz |
13 |
|
14 |
|
15 |
|
16 |
On Fri, Feb 19, 2010 at 3:42 PM, Chris Bandy <cbandy@××××××.com> wrote: |
17 |
> Ladislav Laska wrote: |
18 |
>> Sure we can, in fact, it was like this until recently. |
19 |
>> |
20 |
>> Well, I've grepped ebuilds and found 43 with EAPI=0/1 and more with no |
21 |
>> EAPI set. That's a lot of packages and since I don't have time to fix |
22 |
>> all of them, I'll commit workaround. Feel free to remove it when all |
23 |
>> packages are fixed. |
24 |
>> |
25 |
>> Regards Ladislav Laska |
26 |
>> S pozdravem Ladislav Laska |
27 |
>> --- |
28 |
>> xmpp/jabber: ladislav.laska@××××××.cz |
29 |
>> |
30 |
> |
31 |
> Thank you very much. If porting from EAPI=1 to 2 is as simple as your |
32 |
> commit for my two packages, I'd be happy to test some others and submit |
33 |
> patches. |
34 |
> |
35 |
> Does it make sense to emit a QA/warning when you find PATCHES in EAPI=0|1 ? |
36 |
> |
37 |
> -- Chris |
38 |
> |
39 |
> |