[tex-live] Package preparation question (directory structure)
karl at freefriends.org
Sun Sep 8 00:25:27 CEST 2013
will have a 'lily-' prefix which is less ugly than lgl- and should
definitely be sufficient with regard to unique file-names.
Unless there are other Lilypond-related packages (not in TeX) which use
such names ... That's why the ugly lgl- came to mind.
Exactly, this is 'import'ed by the other scripts. I do not see why
this complicates things,
Because the gen*Command scripts will be in the bin/ directory, but
lilyglyphs_common.py should not be, since it's not meant to be invoked
directly. PATH directories should not be cluttered with
So, you have to do something in the user-level scripts so that it can
find the common script. As far as Python (in TL) goes, I believe you
will be breaking new ground here, sorry to say.
For TL, the files will installed be like this:
bin/i386-linux/lgl-genImageCommand [as a symlink, but that's irrelevant here]
So it's not trivial to locate the common file. We don't and can't do
anything about PYTHONPATH or anything like that.
I think the most reliable way to find it is by running something like
(sh-ish syntax for example):
com=`kpsewhich --progname=lilyglyphs --format=texmfscripts lilyglyphs_common.py`
And then read in $com. I don't know how hard or easy that may be in the
Hope this helps,
More information about the tex-live