Hi! On Sun, 2009-08-02 at 13:54:24 +0200, Frans Pop wrote: > Package: dpkg > Version: 1.15.3.1 > Severity: wishlist > Tags: patch > > When the output of package installations are logged to a file, the > progress counter updates while reading the database are distracting.
It should only get updated if stdout is a tty. In the same way most other programs do it, including apt for example. > This is especially the case in Debian Installer where multiple package > installations are started and all are logged to the syslog. For an > example of the result, see the syslog attached in [1]. > > Another example is buildd logs, for example [2]. I'm guessing this logging is taken from the tty directly instead of redirecting stdout? If so, OOC what was the reason to do it that way? Also you'll notice that in normal conditions this works just fine, see 00:10:32, 00:10:39, etc. And when it does not work (on in-target) it does not work only for dpkg but for other stuff as well, see 01:12:27. On the build logs the same happens, some parts work ok, others not, I'm guessing a similar issue with not just redirecting stdout. > The attached patch adds an option --no-db-progress that allows to suppress > the progress updates in such situations. > > If you'd like any changes (maybe a more generic name for the option?) or > if I've forgotten anything, then please let me know. Hmm, this options is too specific, and I'd like dpkg to automatically do the right thing, OTOH most apps do fancier stuff when they know they are running on a tty, and if one reads from the tty directly it's expected to get garbage. That does not mean we could not add something like a --quiet option, though, but I'd rather understand first what and why of the current situation. regards, guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
