juergbi commented on issue #2150: URL: https://github.com/apache/buildstream/issues/2150#issuecomment-5070894222
Even if we all were to agree that non-verbose might be a better default (maybe keep verbose as default for non-interactive mode), I'm not sure whether changing the default within 2.x would be a good idea. > Having to instruct every user to turn this off I can certainly see the verbose output being overwhelming for some users. However, it's not like BuildStream won't function with the verbose output for those users. If the default verbose output is really confusing to a majority of users of particular projects, I'm wondering whether it might be reasonable to allow projects to define defaults for the user config. I.e., if the user doesn't explicitly set `verbose` in the config file and also doesn't pass `--verbose` or `--no-verbose`, use the project-defined default. A project default for `message-format` could also be interesting. I'm not sure whether it's a good idea, though, especially as it might not straight forward given logging may start before `project.conf` is read and subproject defaults would presumably have to be ignored. A simpler possibility could be to print a message very early indicating that verbose logging is enabled and how to disable it for more concise output. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
