Hello!
I'd love to have whizzytex installable with Texlive in etch. Therefore
I did test some things and am offering help to resolve any remaining
questions.
I tested building and running whizzytex with Texlive.
Building dependencies:
----------------------
Building the documentation needs several style files which I found in
three texlive-* packages. This leads to the following build dependencies:
"( texlive-latex-extra, texlive-pstricks, texlive-latex-base ) | tetex-extra".
As I think one cannot write it as that I used the following equivalent line:
"texlive-latex-extra | tetex-extra , texlive-pstricks | tetex-extra,
texlive-latex-base | tetex-extra".
Note I did write the Texlive packages before the Tetex ones to actually use
them for testing. Reversing the order might be the less invasive change. On
the other hand Texlive is going to be the default Tex "distribution"
in the future.
Runtime dependencies:
---------------------
The current package depends on tetex-bin, which in turn depends on
tetex-base. When both are installed, then tex binaries and basic
format packages are present.
With Texlive it is the other way round: texlive-base depends on
texlive-base-bin and together they bring binaries and formats.
So "texlive-base | tetex-bin (version..)" seems appropriate.
Summing up:
-----------
You will find the resulting control file as attachment. I've tested
building withing current sid chroot using pbuilder and running
the resulting package on both Debian stable and testing (xemacs only).
Do you think this change is suitable for an upload targeted at etch?
If not, what remains to be done? Whizzytex is one of a few if not the
last package, which is not installable with Texlive and I would love
to change that.
Regards
Florian
--
Florian Hinzmann private: [EMAIL PROTECTED]
Debian: [EMAIL PROTECTED]
PGP Key / ID: 1024D/B4071A65
Fingerprint : F9AB 00C1 3E3A 8125 DD3F DF1C DF79 A374 B407 1A65
control
Description: Binary data
