| 1 |
On Mon, 5 Jul 2010 18:34:38 +0200 |
| 2 |
Arfrever Frehtes Taifersar Arahesis <Arfrever@g.o> wrote: |
| 3 |
> You should read relevant part of comment #7: |
| 4 |
> "The colors can of course be continued to be used in outputs that are |
| 5 |
> purely build time outputting and not for communicating things for |
| 6 |
> users like what cmake builds do." |
| 7 |
> |
| 8 |
> python.eclass uses colors for build time outputting, which doesn't |
| 9 |
> communicate anything for users. |
| 10 |
|
| 11 |
Well stop it. You're cluttering up your eclass with pointless junk |
| 12 |
under the mistaken impression that more complicated eclasses are |
| 13 |
better. If you have a desperate need for a coloured output that isn't |
| 14 |
doable using the existing e* functions, make your case for either a new |
| 15 |
EAPI or for a special, dedicated eclass. |
| 16 |
|
| 17 |
Besides, if you're not communicating anything for users, why have it |
| 18 |
there? |
| 19 |
|
| 20 |
-- |
| 21 |
Ciaran McCreesh |
Archives