[tex-live] TDS and binaries / man pages

Zdenek Wagner zdenek.wagner at gmail.com
Thu Mar 19 16:41:17 CET 2009

2009/3/19 Daniel Becker <daniel.becker at uni-rostock.de>:
> ...
> I had a second look at http://www.ctan.org/tex-archive/tds/tds.pdf (Section
> 3.6)
> As the package contains a perl-script and a java class file my reading is
> that they should go in
> /scripts/splitindex/splitindex.class
> /scripts/splitindex/splitindex.pl
It should be script/splitindex/..., not /scripts/splitindex/...
because users do not have write access to the root directory and are
not allowed to create the /scripts directory.

> But only those. See below
>> My opinion is that the .tds.zip won't be directly usable (ie, just unzip
>> at the
>> root of your TEXMFHOME) by users, and that in TeX Live we don't really
>> care,
>> since our scripts can move things as we like.
> Ok, thanks. Does that mean that a package that contains binaries and man
> pages cannot be packaged in a TDS-compliant way? As some additional action
> is required anyway, what about putting the bin and the man folders inside
> /source? (tds.pdf: "The TDS leaves unspeciï¬ ed any structure under
> source.")
> texmf/source/latex/splitindex/bin/
> texmf/source/latex/splitindex/man/
> texmf/source/latex/splitindex/ + other files (.dtx, .ins, ....)
> The advantage would be that a user who unzips the tds.zip doesn't get
> "strange" directories at the top level, but only in the
> /source/latex/splitindex/ directory. This still does not mean that a user
> that unpacks in a local texmf-tree gets something usable. But at least the
> local texmf-tree is not cluttered.
> Daniel

Zdeněk Wagner

More information about the tex-live mailing list