Bug#264043: trying to get to the core of the jadetex vs etex issue
Hilmar Preusse <hille42@web.de> writes:
> I think #253098 is a mixture of different bugs. First they speak
> about wrong usage of tail and mktemp not regarding $TMPDIR and later
> about the incompatible change in tetex.
Yes. That is *all* #253098 should be about. I'm downgrading the bug
to normal severity.
That means that if tetex-bin 2.0.2-17 is breaking jadetex install, I
don't have any bugs filed on my package to that effect. I haven't yet
been able to reproduce the error.
>> (jadetex could then either switch to E-TeX and depend on tetex-bin
>> (>= 2.0.2-17) or stay unchanged and conflict with tetex-bin (=
>> 2.0.2-17) ).
>>
> No, if we create again latex.fmt and pdflatex.fmt that checkfmt
> commands from jadetex 3.13-1 will not fail, so we don't have to set
> these restrictions.
Well, that would be great, and I can create the conflicts.
Lets step back a second. The only reason I do 'checkfmt latex.fmt'
(etc) is that I wanted it to be obvious if fmtutil is breaking because
of problems that tetex-bin might be having in producing memory dumps
which are prerequisites for building a jadetex memory dump. I never
intended to have "special needs" or to require "special formats".
I can easily modify my routine to check for latex.fmt or latex.efmt,
or only the later, or whatever. However, as I understand it, for this
check to work properly, it must match what we're using in fmtutil.cnf.
I guess the real question in my mind is what fmtutil.cnf needs to look
like for JadeTeX to work properly, but minimizing any radical changes
so Debian can proceed with the freeze. Right now it is like so:
jadetex tex language.dat &latex jadetex.ini
pdfjadetex pdftex language.dat &pdflatex pdfjadetex.ini
Given this fmtutil.cnf, my understanding is that it is indeed true
that prerequesites for building jadetex are latex.fmt, pdftex.fmt and
pdflatex.fmt . What I'm hearing from Hilmar is that these plain TeX
memory dumps are no longer produced (althought they can be hanging
around), because in tetex-bin, LaTeX switched to eTeX.
I certainly don't want to require tetex-bin post-install to take 3
times longer just for jadetex's sake. I can switch around the
postinst and the fmtutil.cnf to switch to eTex -- that is, once
I'vetested that that actually works with Jade and OpenJade.
--
.....Adam Di Carlo....adam@debian.org.....<URL:http://www.debian.org/>
Reply to: