[tex-live] texconfig init

[Karl Berry]

    Is there any good reason to run updmap from "texconfig init" at all?

As I understand it (from what Thomas just told me), the (or a) purpose
of texconfig init is to regenerate what is in texmf-var, which includes
the updmap-generated files.  So 

    Either people can run updmap separately or it can be made an
    additional option, so that people can say "texconfig updmap".

By the same token, if all you want to do is run fmtutil, then you can
run fmtutil --all or --refresh, instead of texconfig init.

    What bothers me most is that, when an error occurs in fmtutil,
    "texconfig init" continues as if nothing had happened.  

I agree that if fmtutil fails, it would be desirable not to go on and
run texlinks and updmap.  Since I gather from Thomas's reply that he
doesn't feel strongly about this, I went ahead and changed the script.

I guess the verbosity of updmap still obscures the verbosity of fmtutil,
but now only if everything succeeds.  We could also run updmap --quiet,
but then there is a potentially long pause while apparently nothing is
happening, which doesn't seem desirable either.  So maybe this is the
best compromise for now.

k