[1950] in athena10
debathena-tex-config (was: Re: /svn/athena r23668 - in trunk/debathena/config:
daemon@ATHENA.MIT.EDU (Evan Broder)
Sun Mar 29 19:00:08 2009
Message-ID: <49CFFD47.2070100@mit.edu>
Date: Sun, 29 Mar 2009 18:59:19 -0400
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: Tim Abbott <tabbott@mit.edu>
CC: debathena@mit.edu
In-Reply-To: <alpine.DEB.1.10.0903291844190.28248@vinegar-pot.mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Tim Abbott wrote:
> Could you give a brief overview as to how this package is expected to
> work?
>
Sure, that sounds like a good idea.
debathena-tex-config uses texconfig to generate the various config files
for letter paper. By setting TEXMFVAR and TEXMFCONFIG, we can override
the destination for the files that texconfig generates. We generate the
actual config files into SRC/files/etc/texmf.
When updating the paper settings for pdftex, texconfig also runs
`fmtutil --refresh`, which regenerates the TeX format files. These are
all generated files, and we can re-generate them at install time, so we
drop them into SRC/junk, where they're ignored.
We then find all files in SRC/files/etc/texmf and install them into the
corresponding path in DEB_DESTDIR, appending .debathena to the filename
for config-package-dev to use (note that TEXMFCONFIG is a relative path).
Finally, config-package-dev gets its list of files to divert by running
a `find` in SRC/files. It does the find in SRC/files instead of in
DEB_DESTDIR because the variable gets evaluated at the start of each
target where it's used, instead of when it's used, meaning that the
files may not have been installed into DEB_DESTDIR when the variable is
being evaluated.
When the package is installed or removed, a postinst/postrm runs
`fmtutil-sys --refresh` to make sure that all of the generated files are
appropriately regenerated.
And...I think that's basically everything.
- Evan
