Subject: Re: [patch] Unified progress and error messages
To: Roland Illig <rillig@NetBSD.org>
From: Mark E. Perkins <perkinsm@bway.net>
List: tech-pkg
Date: 02/18/2006 17:57:12
On 2006/02/18 16:01, Roland Illig wrote:
> Hi,
> 
> currently the use of progress messages in pkgsrc is not as consistent as
> it could be. For example:
> 

<snip>

> but has the same leader. So I suggest to change the above to look like:
> 
> ===> Checking for vulnerabilities in pkglint-4.57
> ===> Extracting for pkglint-4.57
> => Required installed package digest>=20010101: digest-20050731 found
> => Required installed package perl>=5.0: perl-5.8.7nb8 found
> ===> Patching for pkglint-4.57
> ===> Overriding tools for pkglint-4.57
> ===> Configuring for pkglint-4.57
> => Setting compile-time constants for pkglint.
> ===> Installing for pkglint-4.57
> => Creating installation directories
> => [Automatic manual page handling]
> => Registering installation for pkglint-4.57
> => Checking for work-directory references in pkglint-4.57
> => Checking for non-existent script interpreters in pkglint-4.57
> ===> Packaging pkglint-4.57
> => Building binary package for pkglint-4.57
> 

<snip>

My preference would be to have the *text* for the steps is indented more
than the *text* for the stages:

=> Checking for vulnerabilities in pkglint-4.57
=> Extracting for pkglint-4.57
===> Required installed package digest>=20010101: digest-20050731 found
===> Required installed package perl>=5.0: perl-5.8.7nb8 found
=> Patching for pkglint-4.57
=> Overriding tools for pkglint-4.57
=> Configuring for pkglint-4.57
===> Setting compile-time constants for pkglint.
=> Installing for pkglint-4.57
===> Creating installation directories
===> [Automatic manual page handling]
===> Registering installation for pkglint-4.57
===> Checking for work-directory references in pkglint-4.57
===> Checking for non-existent script interpreters in pkglint-4.57
=> Packaging pkglint-4.57
===> Building binary package for pkglint-4.57


Even better, IMO, would be to use the same leader everywhere, but to
have the text for the steps indented more than the text for the stages
(the additional white space helps even more to set things apart
visually, which is part of what I think you are trying to accomplish):

=> Checking for vulnerabilities in pkglint-4.57
=> Extracting for pkglint-4.57
=>   Required installed package digest>=20010101: digest-20050731 found
=>   Required installed package perl>=5.0: perl-5.8.7nb8 found
=> Patching for pkglint-4.57
=> Overriding tools for pkglint-4.57
=> Configuring for pkglint-4.57
=>   Setting compile-time constants for pkglint.
=> Installing for pkglint-4.57
=>   Creating installation directories
=>   [Automatic manual page handling]
=>   Registering installation for pkglint-4.57
=>     Checking for work-directory references in pkglint-4.57
=> Checking for non-existent script interpreters in pkglint-4.57
=> Packaging pkglint-4.57
=>   Building binary package for pkglint-4.57

or use the '===>' leader everywhere.

Cheers,
Mark