Mail-Followup-To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
References: <20060427182251.GA23586@m0A023293.vpn.uni-freiburg.de>
            <200605042048.k44KmDO23074@f7.net>
            <20060505043642.GB3369@irwin.vpn.uni-freiburg.de>
            <17499.5320.136951.598853@morse.mittelbach-online.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Message-ID:  <20060506232642.GA3790@irwin.vpn.uni-freiburg.de>
Date:         Sun, 7 May 2006 01:26:42 +0200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Heiko Oberdiek <oberdiek@UNI-FREIBURG.DE>
Subject: Re: LaTeX Release 2005/12/01
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <17499.5320.136951.598853@morse.mittelbach-online.de>
Precedence: list
Status: R

On Fri, May 05, 2006 at 11:03:04AM +0200, Frank Mittelbach wrote:

> Getting the  distribution in a better shape should always be a goal. How much
> of what you have done is or can be automated?

The main job is done by a quite simple perl script that
runs the manually determined program calls.
To generate all, I only call
  ./build.sh

But the interesting part is how to get the TDS archive
from a "wild" collection of files of a directory.

* If the .ins file supports the TDS feature, then
  the installation of the generated files is easy,
  just running docstrip. The missing directories can be
  created by the shell-escape feature:
  For this purpose I am using the following docstrip.cfg:

%%% docstrip.cfg
\BaseDirectory{texmf}
\UseTDS

\def\shell#{\immediate\write18 }
\def\mkdir#1{\shell{mkdir -p #1}}

\let\saved@usedir\usedir
\def\usedir#1{%
  \mkdir{\basedir#1}%
  \saved@usedir{#1}%
}
%%% docstrip.cfg %%%

* Manual part of .ins file based installatoin:
  * Which .ins files must be used (there can be a master .ins file).
  * \usedir isn't always correct, e.g. babel puts driver.drv and user.drv
    in the TDS:tex tree.

* Even if there are .ins files, then there can be files, that
  must copied directly into the TDS:tree, because they are not
  covered by a dtx file (latex/base: testpage.tex, idx.tex, ...)

* Deciding, which files goes into the TDS:source tree.

* Generating the documention is the most difficult part:
  * Installation of additional packages. (E.g., I had to install
    some font packages (armenian, tipa, wsuipa, fc).
  * Number and order of latex, makeindex, ... runs.
  * Sometimes hyperref support is tricky (e.g. for adding
    bookmarks that are not set by default).
  * The example a.ps in grfguide is quite unhappy. The example
    and the explanation in the text is not too good:
    By specifying a wrong BoundingBox the viewport feature
    is emulated. This works for dvips, but not for pdfTeX.
  * ...

Yours sincerely
  Heiko <oberdiek@uni-freiburg.de>