Re: Adding a verbose flag.

[A Johnston <ajohnston54637@gmail.com>]

"Please be more verbose as to where we should add the verbose flag..."

Verbosity is traditionally done with levels. Here is a potential set:

0 - Quiet: No news is good news.
1 - Normal: As it currently is.
2 - Verbose: At the granularity of a bash statement or equivalent.
3 - Trace: Individual bash command or equivalent.

To add these I would start at the top level update.sh and release.sh and
try to add a diagnostic for everything invoked by those. I wouldn't want
to modify existing code unless there was a clear need and so there may
be a degree of "best fit" to the placement of diagnostics.

Thank you, I will let you know.

On Tue, Dec 9, 2025 at 10:43 PM Alexander Kjäll <alexander.kjall@gmail.com> wrote:

Thanks for reporting back about the experience as a new user, its very easy to become blind to those things.

Please make a pull request with an improvement :)

//Alex

On Wed, Dec 10, 2025, 06:10 Blair Noctis <ncts@debian.org> wrote:

-> A Johnston <ajohnston54637@gmail.com>, 2025-12-09T15:24:50-0800 ->
> Hello,
>
> My experience getting started was that I had to debug the packaging
> process immediately. Once I had things figured out I was able to avoid
> the cracks and so things didn't seem that bad anymore.
>
> However, I'd like to suggest that the cold start experience would be a
> lot better with a verbose flag. I am happy to add it.
>

Please be more verbose as to where we should add the verbose flag...

--
​    ,Sdrager
Blair Noctis

🇵🇸