Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

check-fmri output lines should be self-contained #25

Closed
mtelka opened this issue Jul 30, 2024 · 0 comments
Closed

check-fmri output lines should be self-contained #25

mtelka opened this issue Jul 30, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@mtelka
Copy link
Contributor

mtelka commented Jul 30, 2024

The new check-fmri output is easily readable for humans, but it is hard(er) for automatized handling. For example when I do something like this:

$ target/release/oi-pkg-checker check-fmri runtime/perl | grep developer
[INFO]     developer/appcert
[INFO]     developer/build/ant
[INFO]     developer/build/autoconf-213
[INFO]     developer/build/automake-110
[INFO]     developer/build/automake-111
[INFO]     developer/build/automake-115
[INFO]     developer/build/automake-116
[INFO]     developer/build/onbld
[INFO]     developer/debug/valgrind
[INFO]     developer/dtrace/toolkit
[INFO]     developer/object-file
[INFO]     developer/versioning/git
[INFO]     developer/ant
[INFO]     developer/autoconf-2.13
[INFO]     developer/automake-1.10
[INFO]     developer/automake-1.11
[INFO]     developer/automake-1.15
[INFO]     developer/automake-1.16
[INFO]     developer/dtracetoolkit
[INFO]     developer/git
[INFO]     developer/pkgbuild
[INFO]     developer/sloccount
[INFO]     developer/valgrind
$

then it is unclear what kind of output (dependencies) I see there.

It would be great if there is some way how to switch back to the previous full output. For example using the --verbose option or so.

@aueam aueam added the enhancement New feature or request label Aug 1, 2024
@aueam aueam closed this as completed in 27edb2a Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants