seth vidal wrote :
If we could get rpm to be silent and have all of the messages (stderr
or
stdout) be presented back to us as part of the callback I think most of
us would be quite happy. If only b/c it would mean we would then have
the option of echoing it back to the user, saving it to a log or both.
I couldn't agree more. I find it plain silly to almost always have to
execute "foo args &>/dev/null || :" in scriplets, when getting the
output of the command as well as knowing if it actually failed or
succeeded can be interesting information. If we could have a log file
of rpm operations output, it would be really great.
*BUT* this does mean breaking backwards compatibility in many cases
(i.e. having failing scriplets leave duplicate packages in the rpmdb).
Matthias
--
Clean custom Red Hat Linux rpm packages :
http://freshrpms.net/
Fedora Core release 5.92 (FC6 Test3) - Linux kernel 2.6.18-1.2759.fc6
Load : 0.36 0.51 0.37