Hi
thanks for your bug report and analysis, but could you please
send this to
tex-l...@tug.org
Of course I can forward it, but then the discussion would probably
be held between me and upstream TeX Live, and there will be
quite some discussion. You can drop the whole Debian specific
part (if you want).
Some remarks only on the patches:
> verbose()
> {
> - $mktexfmtMode && ${1+"$@"} >&2 || ${1+"$@"}
> + if $mktexfmtMode
> + then
> + ${1+"$@"} >&2;
> + else
> + ${1+"$@"};
> + fi
> }
I see your point here, but I am far from convinced. Thomas Esser wrote
this part *long*long* time ago, and he is known for excellent
programming work. He surely had an intention behind this code,
otherwise he would not write it like that.
> if test -f "$fmtfile"; then
> grep '^! ' $format.log >/dev/null 2>&1 &&
> - log_warning "\`$engine -ini $tcxflag $jobswitch $prgswitch $texargs'
> possibly failed."
> + log_failure "\`$engine -ini $tcxflag $jobswitch $prgswitch $texargs'
> possibly failed."
I am not sure - but probably this makes sense in Debian, but not
anywhere else. The problem is we don't want fmtutil to stop
but continue building other formats.
Imagine root calling
fmtutil-sys --all
to rebuild all formats, and one is failing. Then we don't want to
stop there, but continue building, right?
Same with the other log_warning/_failure change
Norbert
------------------------------------------------------------------------
PREINING, Norbert http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
