[Rpm-maint] [RFC] Move all informative messages to stderr by default (ticket #31)

Michael Schroeder mls at suse.de
Tue Oct 25 13:48:45 UTC 2016


On Tue, Oct 25, 2016 at 11:20:14AM +0300, Panu Matilainen wrote:
> On 10/13/2016 09:41 AM, Panu Matilainen wrote:
> > Rpm has always spewed all sorts of "informative" messages into stdout
> > where it gets mixed up with user requested information such as query
> > output, complicating scripts unnecessarily and also breaking unix
> > traditions.
> > 
> > Make the user-requested output (namely query and verify output) go to
> > stdout by explicitly fprintf()'ing it there, and all of rpmlog()
> > output goes to stderr (or other specified logfile).
> > 
> > Fixes rpm.org ticket #31, RhBug:1358861, RhBug:247239, RhBug:439290...
> > OTOH it *will* break scripts people use for querying etc. Making
> > scripts compatible with both old and new behavior shouldn't be hard, but
> > it does require changes and some *will* complain. So obviously not
> > 4.13 material, target would be the next major release after that.
> > 
> > Comments, thoughts?
> 
> Ping? No comments at all on a proposal that'd likely break half the scripts
> created around rpm queries?

What about library users? Seems like they will no longer receive
the output via the rpmlog callback if you just write to stdout.

Cheers,
  Michael.

-- 
Michael Schroeder                                   mls at suse.de
SUSE LINUX GmbH,           GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}


More information about the Rpm-maint mailing list