The installer knows where texlive is located because it's registered
with the OS under the $TEXMFDIST variable. If that variable isn't
defined, I would assume that the post install script would fail, so
you'd end up with gregorio installed in the directory you specified
(because that isn't handled by the post install script, but by the
installer itself), but not in texlive/bin, nor in the $PATH. I'm not
sure why we don't try to add the gregorio installation directory to
$PATH. The way it is is the way it was when I started helping out and I
don't know how to make it do anything different so I've just worked with
what was there.
The svn is out of date. We've moved over to github now:
https://github.com/gregorio-project/gregorio
Gregorio is coded in a combination of languages:
C is used for the most of the main script that converts gabc to gtex
(and gxml, but I don't know of anyone using that).
TeX is used for gregoriotex, but there are also some lua scripts that
help things along.
Lua is used for a bunch of helper scripts here and there.
Python gets used in the scripts that build the fonts
Fontforge is used to create the base glyphs for the fonts (not really a
language, but rather a font creation tool)
make (if you can call that a language) is used in the makefiles which
are used to automate the build process on Mac and Linux
I don't think this is exhaustive, as the installation instructions list
the following package dependencies for building from source:
gcc, automake, libltdl-dev, libtool, libxml2, libxml2-dev, flex, bison,
python, autoconf, texlive and make
✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
_______________________________________________
Gregorio-users mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-users
