We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
--verbose
The text was updated successfully, but these errors were encountered:
27edb2a
No branches or pull requests
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: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.The text was updated successfully, but these errors were encountered: