[twg-tds] storing scripts in the texmf tree

Olaf Weber olaf at infovore.xs4all.nl
Wed Feb 11 18:54:46 CET 2004

Hans Hagen writes:
> At 00:21 10/02/2004, Thomas Esser wrote:

>> To answer Karl's question about the benefit:
>> - we solve the problem for one-file packages (for all languages)
>> - it all looks cleaner and more reliable if we can say
>>   kpsewhich -format=scripts thumbpdf.pl
>>   kpsewhich -format=scripts texexec.pl
>> instead of
>>         kpsewhich -progname=perl -format='other text files' thumbpdf.pl
>>         kpsewhich -progname=context -format='other text files' texexec.pl

> yeah ... (it would simplify my texmfstart.rb script -)

>> Searching texmf/foo// by using
>> kpsewhich -progname=foo -format='other text files'
>> if foo is nothing like a program but a logical concept (or package
>> name) seems like a dirty trick anyway...

> indeed, the 'other text files/binaries' has become fuzzy/overloaded anyway

> just wondering: maybe kpsewhich can be extended by something

>    in texmf.cnf:   format.whatever pathspec
>    in kpsewhich:   -format=whatever

> or so ...

Perhaps I haven't followed the discussion in sufficient detail, but
the proposed semantics of this extension aren't clear to me.

Olaf Weber

               (This space left blank for technical reasons.)

More information about the twg-tds mailing list