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