1 |
I love it - this is similar to the xorg log output, and i think it makes |
2 |
the portage output much cleaner and easier to read. |
3 |
|
4 |
El mar., 28 de septiembre de 2021 11:36 a. m., Michał Górny < |
5 |
mgorny@g.o> escribió: |
6 |
|
7 |
> Hi, everyone. |
8 |
> |
9 |
> I know I'm going to regret asking this... but I've prepared a change to |
10 |
> the Portage output format and I think it asks for a wider discussion |
11 |
> than internally in Portage team. |
12 |
> |
13 |
> The primary problem with the current output format is that different |
14 |
> kinds of messages differ only in color. This makes them |
15 |
> indistinguishable without colors and hard to grep. ago's been asking |
16 |
> for a better way to grep for QA warnings and this is pretty much what |
17 |
> motivated me to do this. |
18 |
> |
19 |
> The proposed new format distinguished message types both using colors |
20 |
> and strings. This is roughly inspired by Xorg logs. For example, |
21 |
> instead of: |
22 |
> |
23 |
> * some message |
24 |
> * other message |
25 |
> * hell if i know what this is |
26 |
> |
27 |
> You get: |
28 |
> |
29 |
> [WW] some message |
30 |
> [EE] other message |
31 |
> [QA] hell if i know what this is |
32 |
> |
33 |
> I've also added more colors to explicitly distinguish einfo from elog, |
34 |
> and ewarn from eqawarn. Then, I've replaced most of '>>>' and '!!!' |
35 |
> used by Portage with four-character versions to keep messages aligned. |
36 |
> The 'zings' used for merging files remain three-character, so now it's |
37 |
> easily possible to distinguish messages from installed file list. |
38 |
> |
39 |
> The PR doing this is: https://github.com/gentoo/portage/pull/759 |
40 |
> |
41 |
> Example screenshot: |
42 |
> |
43 |
> https://user-images.githubusercontent.com/110765/135119090-16e9599d-1b0f-41b8-a965-a55577183ffd.png |
44 |
> |
45 |
> -- |
46 |
> Best regards, |
47 |
> Michał Górny |
48 |
> |
49 |
> |
50 |
> |
51 |
> |