Bug#403641: tetex-base: postrm fails if just unpackaged.

[Florent Rougon <f.rougon@free.fr>]

Frank Küster <frank@debian.org> wrote:

> Why is --quiet only used for update-updmap?  It's the same script behind
> the three, and with "-v" it always says

IMHO, it's a bug that --quiet isn't used for all three calls. But this
--quiet here dates from before we introduced
dhit_check_run_without_errors(). With this function, the output of the
three update-* calls is redirected to a file, so whether using --quiet
or not is not that important.

I believe we should still call all of them with --quiet in this context,
because most of the info that comes in without this option is
user-oriented and misleading in case of a package installation:

    echo "$progname has updated '$output_file'. If you want to"

    if [ "$progname" = "update-language" ]; then
        echo "enable the new patterns, you should run fmtutil-sys or fmtutil"
        echo "(with option --all, or with a particular format specified)."
    elif [ "$progname" = "update-updmap" ]; then
        echo "enable the map files with this new file, you should run" \
             "updmap-sys or updmap."
    elif [ "$progname" = "update-fmtutil" ]; then
        echo "enable the new formats,  you should run fmtutil-sys or fmtutil"
        echo "(with option --all or --missing)."

This info is really intended for users running the update-* scripts
manually.

> ${progname}'s -v option is deprecated. The default mode of operation will
> be verbose as soon as enough packages use the --quiet option. Please update
> your scripts accordingly.\n\n" >&2; quiet=0; shift ;;

Yeah, we should really do the switch to verbose mode right after the
release of etch. Otherwise, we can still wait...
It's a pity we didn't do it for etch. :-|

-- 
Florent