[gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-28 Thread Michał Górny
Hi, everyone. I know I'm going to regret asking this... but I've prepared a change to the Portage output format and I think it asks for a wider discussion than internally in Portage team. The primary problem with the current output format is that different kinds of messages differ only in color.

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-28 Thread Wolfgang E. Sanyer
I love it - this is similar to the xorg log output, and i think it makes the portage output much cleaner and easier to read. El mar., 28 de septiembre de 2021 11:36 a. m., Michał Górny < mgo...@gentoo.org> escribió: > Hi, everyone. > > I know I'm going to regret asking this... but I've prepared a

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-28 Thread Ulrich Mueller
> On Tue, 28 Sep 2021, Michał Górny wrote: > The proposed new format distinguished message types both using colors > and strings. This is roughly inspired by Xorg logs. Using the same markers as Xorg (especially [--]) but with different meaning may be confusing though. Xorg has these: M

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-28 Thread Michał Górny
On Tue, 2021-09-28 at 18:26 +0200, Ulrich Mueller wrote: > > > > > > On Tue, 28 Sep 2021, Michał Górny wrote: > > > The proposed new format distinguished message types both using > > colors > > and strings. This is roughly inspired by Xorg logs. > > Using the same markers as Xorg (especially [--

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-28 Thread Ulrich Mueller
> On Tue, 28 Sep 2021, Michał Górny wrote: > On Tue, 2021-09-28 at 18:26 +0200, Ulrich Mueller wrote: >> Markers: (--) probed, (**) from config file, (==) default setting, >> (++) from command line, (!!) notice, (II) informational, >> (WW) warning, (EE) error, (NI) not implemented,

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-28 Thread Hank Leininger
On 2021-09-28, Ulrich Mueller wrote: > > On Tue, 28 Sep 2021, Michał Górny wrote: > > On Tue, 2021-09-28 at 18:26 +0200, Ulrich Mueller wrote: > >> Markers: (--) probed, (**) from config file, (==) default > >> setting, > >> (++) from command line, (!!) notice, (II) info

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-29 Thread A Schenck
On 9/28/21 8:36 AM, Michał Górny wrote: > Hi, everyone. > > I know I'm going to regret asking this... but I've prepared a change to > the Portage output format and I think it asks for a wider discussion > than internally in Portage team. > > The primary problem with the current output format is tha

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-29 Thread Francesco Riosa
Il giorno mer 29 set 2021 alle ore 23:52 A Schenck ha scritto: > On 9/28/21 8:36 AM, Michał Górny wrote: > > Hi, everyone. > > > > I know I'm going to regret asking this... but I've prepared a change to > > the Portage output format and I think it asks for a wider discussion > > than internally i

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-29 Thread Sam James
> On 29 Sep 2021, at 22:52, A Schenck wrote: > > [snip] > Didn't expect to be the only dissenting opinion on something like this > but. . . Some applications parse portage output looking for these > 'zings'. At very least app-portage/kuroo does it this way; there must be > others, right? This

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-29 Thread Fabian Groffen
Hi, Would it be possible to have some switch (e.g. --style=legacy) that controls this new vs. the old behaviour? Would perhaps allow applications that parse the output to work via setting this in the global opts. In addition, much like the colour map, how do you see this change in light of eclas

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-29 Thread Michał Górny
On Thu, 2021-09-30 at 08:40 +0200, Fabian Groffen wrote: > Hi, > > Would it be possible to have some switch (e.g. --style=legacy) that > controls this new vs. the old behaviour? Would perhaps allow > applications that parse the output to work via setting this in the > global opts. Patches welcom

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-09-30 Thread Fabian Groffen
On 30-09-2021 08:44:33 +0200, Michał Górny wrote: > On Thu, 2021-09-30 at 08:40 +0200, Fabian Groffen wrote: > > Hi, > > > > Would it be possible to have some switch (e.g. --style=legacy) that > > controls this new vs. the old behaviour? Would perhaps allow > > applications that parse the output

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-01 Thread A Schenck
On 9/29/21 11:44 PM, Michał Górny wrote: > On Thu, 2021-09-30 at 08:40 +0200, Fabian Groffen wrote: >> Hi, >> >> Would it be possible to have some switch (e.g. --style=legacy) that >> controls this new vs. the old behaviour? Would perhaps allow >> applications that parse the output to work via set

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-01 Thread Alec Warner
On Fri, Oct 1, 2021 at 11:30 AM A Schenck wrote: > > On 9/29/21 11:44 PM, Michał Górny wrote: > > On Thu, 2021-09-30 at 08:40 +0200, Fabian Groffen wrote: > >> Hi, > >> > >> Would it be possible to have some switch (e.g. --style=legacy) that > >> controls this new vs. the old behaviour? Would per

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-01 Thread Joshua Kinard
On 9/30/2021 02:40, Fabian Groffen wrote: > Hi, > > Would it be possible to have some switch (e.g. --style=legacy) that > controls this new vs. the old behaviour? Would perhaps allow > applications that parse the output to work via setting this in the > global opts. Perhaps this would be better

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-01 Thread A Schenck
On 9/29/21 3:58 PM, Francesco Riosa wrote: > Il giorno mer 29 set 2021 alle ore 23:52 A Schenck > mailto:lane_and...@hotmail.com>> ha scritto: > > On 9/28/21 8:36 AM, Michał Górny wrote: > > Hi, everyone. > > > > I know I'm going to regret asking this... but I've prepared a > ch

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-02 Thread Michał Górny
On Fri, 2021-10-01 at 18:00 -0400, Joshua Kinard wrote: > On 9/30/2021 02:40, Fabian Groffen wrote: > > Hi, > > > > Would it be possible to have some switch (e.g. --style=legacy) that > > controls this new vs. the old behaviour? Would perhaps allow > > applications that parse the output to work v

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-02 Thread Ulrich Mueller
> On Wed, 29 Sep 2021, A Schenck wrote: > On 9/28/21 8:36 AM, Michał Górny wrote: >> [WW] some message >> [EE] other message >> [QA] hell if i know what this is >> >> I've also added more colors to explicitly distinguish einfo from elog, >> and ewarn from eqawarn. Then, I've replaced most of

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-02 Thread A Schenck
On 10/1/21 11:32 AM, Alec Warner wrote: > On Fri, Oct 1, 2021 at 11:30 AM A Schenck wrote: >> On 9/29/21 11:44 PM, Michał Górny wrote: >>> On Thu, 2021-09-30 at 08:40 +0200, Fabian Groffen wrote: Hi, Would it be possible to have some switch (e.g. --style=legacy) that controls t

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-02 Thread Mike Gilbert
On Sat, Oct 2, 2021 at 1:25 PM A Schenck wrote: > Further discussion belongs on a different list, but the link provided by > mgorny and repeated by you does not allow collaborating in compliance > with the Gentoo Social Contract. The patches were also posted for review on the gentoo-portage-dev m

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-02 Thread Ionen Wolkens
On Sat, Oct 02, 2021 at 09:22:49AM +0200, Ulrich Mueller wrote: > > On Wed, 29 Sep 2021, A Schenck wrote: > > > On 9/28/21 8:36 AM, Michał Górny wrote: > >> [WW] some message > >> [EE] other message > >> [QA] hell if i know what this is > >> > >> I've also added more colors to explicitly dist

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-02 Thread Ionen Wolkens
On Sat, Oct 02, 2021 at 06:04:36PM -0400, Ionen Wolkens wrote: > On Sat, Oct 02, 2021 at 09:22:49AM +0200, Ulrich Mueller wrote: > > > On Wed, 29 Sep 2021, A Schenck wrote: > > > > > On 9/28/21 8:36 AM, Michał Górny wrote: > > >> [WW] some message > > >> [EE] other message > > >> [QA] hell if

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-02 Thread Ionen Wolkens
On Sat, Oct 02, 2021 at 10:53:37PM -0400, Ionen Wolkens wrote: > Guess there's a lot of other options that could be considered as well. > > --- files > >>> text > * current, it wasn't aligned now that I look at it again > (relying only on color to convey type feels clearly wrong to me) > > --- f

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-02 Thread Fabian Groffen
On 02-10-2021 23:03:56 -0400, Ionen Wolkens wrote: > On Sat, Oct 02, 2021 at 10:53:37PM -0400, Ionen Wolkens wrote: > > Guess there's a lot of other options that could be considered as well. > > > > --- files > > >>> text > > * current, it wasn't aligned now that I look at it again > > (relying o

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-03 Thread Ionen Wolkens
On Sun, Oct 03, 2021 at 08:58:00AM +0200, Fabian Groffen wrote: > On 02-10-2021 23:03:56 -0400, Ionen Wolkens wrote: > > On Sat, Oct 02, 2021 at 10:53:37PM -0400, Ionen Wolkens wrote: > > > Guess there's a lot of other options that could be considered as well. > > > > > > --- files > > > >>> text

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-03 Thread Alexey Sokolov
03.10.2021 07:58, Fabian Groffen пишет: > > FWIW, I like this one. Perhaps even with lowercase > > make[4]: leaving directory src > q* soname lacks version > e* failed to die > For me this reads as some kind of censorship to remove profanities from the output; and my mind is trying to reconstr

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-03 Thread Michał Górny
On Tue, 2021-09-28 at 17:36 +0200, Michał Górny wrote: > I know I'm going to regret asking this... but I've prepared a change to > the Portage output format and I think it asks for a wider discussion > than internally in Portage team. As I suspected, I truly regret sending this mail. I'm dangerou

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-05 Thread Michał Górny
On Thu, 2021-09-30 at 09:18 +0200, Fabian Groffen wrote: > > > Final question, am I understanding correctly that normal lines are not > > > prefixed with something? Would it be, for consistency, alignment, and > > > certainty of selecting rows something to use a prefix for those lines > > > too (a

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-05 Thread Fabian Groffen
On 05-10-2021 09:35:32 +0200, Michał Górny wrote: > On Thu, 2021-09-30 at 09:18 +0200, Fabian Groffen wrote: > > > > Final question, am I understanding correctly that normal lines are not > > > > prefixed with something? Would it be, for consistency, alignment, and > > > > certainty of selecting r

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-05 Thread A Schenck
On 10/2/21 10:51 AM, Mike Gilbert wrote: > On Sat, Oct 2, 2021 at 1:25 PM A Schenck wrote: >> Further discussion belongs on a different list, but the link provided by >> mgorny and repeated by you does not allow collaborating in compliance >> with the Gentoo Social Contract. > The patches were als

Re: [gentoo-dev] [RFC] Portage einfo, elog... output format change

2021-10-05 Thread Rich Freeman
On Mon, Oct 4, 2021 at 2:48 AM Michał Górny wrote: > > On Tue, 2021-09-28 at 17:36 +0200, Michał Górny wrote: > > I know I'm going to regret asking this... but I've prepared a change to > > the Portage output format and I think it asks for a wider discussion > > than internally in Portage team. >