configure scripts have a --quiet option, but config.status does not respect it, so that the configure output is not really "quiet". Would it be OK to add a --quiet option to config.status and have configure pass it?
Secondly, if the --quiet option is used, it is saved and used during config.status --recheck, so there's no way to get back the output except rerunning configure. I think it would be more sensible to not save the --quiet option and only pass it to configure if it was given to config.status --recheck. Would this be acceptable? -- Peter Eisentraut [EMAIL PROTECTED]
