1 |
On 07/05/2010 11:23 PM, Arfrever Frehtes Taifersar Arahesis wrote: |
2 |
> 2010-07-05 21:18:57 Mark Loeser napisał(a): |
3 |
>> Arfrever Frehtes Taifersar Arahesis <Arfrever@g.o> said: |
4 |
>>> 2010-07-05 20:00:11 Mark Loeser napisał(a): |
5 |
>>>> Everyone else has already made valid points. I'm just picking this one |
6 |
>>>> to reply to now. Please remove the colors you have added. If you need |
7 |
>>>> a new function, say "eqawarn", we should have that added in the next |
8 |
>>>> EAPI with a description of when and where to use it. |
9 |
>>> |
10 |
>>> In case of the colored message added in this patch, if einfo/elog/ewarn/eqawarn/eerror was used, |
11 |
>>> then its output wouldn't be logged by Portage. |
12 |
>> |
13 |
>> I don't understand what you are trying to say. |
14 |
> |
15 |
> Portage doesn't log output of einfo/elog/ewarn/eqawarn/eerror called in global scope. |
16 |
> |
17 |
|
18 |
Can you point to the location of python.eclass / distutils.eclass where |
19 |
you need to send output from global scope, please? |