[tex-live] lambda, omega, latex.ini
Fabrice Popineau
Fabrice.Popineau at supelec.fr
Tue May 11 15:05:06 CEST 2004
> Can tpm-factory take a partial TDS tree containing just one package, and
> create
> a TPM?
Actually, it is even simpler than that. Apart from the usual bookkeeping
(looking for missing bits of info in the Catalogue, file sizes, etc), what
does tpm-factory is:
perl tpm-factory.pl --new=Package/foo
create an empty package. There is a correspondence:
Package <-> texmf-dist
Documentation <-> texmf-doc
TLCore <-> texmf
After that, it is expected that all the files for your 'foo' package are
located under directories belonging to this package and unique to it (its
namespace). If foo is a classical package, such locations are:
texmf-dist/tex/${format}/foo/*
texmf-dist/fonts/{afm,type1,vf,tfm,...}/${vendor}/foo/*
etc.
So all you have to do is to pick up a name for your package, put the files
in the tds under locations like texmf-dist/.../foo/ and tpm-factory.pl will
inspect them and build the list of files:
perl tpm-factory.pl --clean --name=Package/foo --arch=all --patterns=auto
Those rules work for texmf-dist and texmf-doc. There are no such rules for
texmf (ie: TLCore). In this case you have to rely on the patterns. Adding
files in texmf is done by editing the texmf/tpm/foo.tpm file, changing the
patterns lists, then:
perl tpm-factory.pl --clean --name=TLCore/foo --arch=all --patterns=from
Checking, especially coverage is done by:
perl tpm-factory.pl --arch=all --type=Package --check=cov > cov.log
(use 'TLCore' and 'Documentation' respectively for --type, or even 'all').
Fabrice
More information about the tex-live
mailing list