The thing is, putting ANYTHING extra into stdout breaks the tool normal 
functionality (which is to emit strictly formatted dependencies on stdout), and 
that is a no-no for debugging options. I don't see how those error messages 
would "never be shown to user" whether redirected or not.
When you're debugging something, you're looking at that output extra carefully, 
no? It's not like we're talking thousands of lines of output here.

All that said, this new suggestion --all-per-file made me realize you must be 
using --rpmfcdebug as the only switch to rpmdeps, which is not the tools normal 
mode of operation at all. So the problem actually is that rpmdeps is not really 
intended to be used as an interactive tool, but only invoked by rpm internally, 
and --rpmfcdebug is a --verbose/--debug style switch that can be enabled 
alongside normal operation to provide extra output for diagnostics - to both 
rpmdeps and rpmbuild.

I think we can work something out. There's two different types of info outputed 
by rpmfcPrint(): one is the classification information which is strictly 
diagnostic extra information. The other side is the generated dependencies, 
which actually are used by rpm, only not in the format printed by rpmfcPrint(). 
Perhaps the two should be separated.

So there could be something like your --all-per-file (maybe just --alldeps?) 
that enables printing of all dependencies, prefixed by their type like 
rpmfcPrint() now does, which is a conflicting option with all the existing 
--requires/--provides etc. Such a mode (to emit all dependency data from a file 
at once) could actually be real-life useful some day if we get to optimizing 
the dependency generation phase.
And --rpmfcdebug only enables output of the classification data.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/220#issuecomment-302619978
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to