Just a warning:
Note that this solutions requires more active support of the
packaging rules. This has been a problem with the Debian package,
where the package maintainer has not had the time to follow the
quick development of LilyPond so the installation has not always
been complete.
/Mats
Reu
> I would advise mimicking the debian approach, installing under TEXMF
> using symlinks, see debian/rules. Even better yet, have make install
> do this if it finds tetex, and move it out of specific distribution
> scripts.
That sounds good.
--
http://www.mupsych.org/~rrt/ | art, n. romanticize
> I welcome all proposals for better solutions,
Doing what Jan suggested, at least in the RPM, seems to be a good way of
sorting things out, at least for RPM-ed systems. After all, it's
reasonable to have only one version of lilypond installed as an RPM.
If people want multiple versions installed
Reuben Thomas wrote:
Yes, and separate scripts for xdvi, dvips, kdvi, gdvi, texi2dvi? I
don't think that this is a good approach.
Need it be scripts? Can't you just make a system call with the TEXMF shell
variable prepended, i.e.
TEXMF=blah
The problem is not the calls from within the lilypon
Han-Wen Nienhuys writes:
>> Perhaps best of all would simply be to install your stuff in TEXMF_LOCAL
>> (if it exists) and otherwise TEXMF. I'm happy to help with getting this
>> working if you think it's a good idea.
While I agree that the lilypond.sh (in fact Red Hat's profile.d) is a
bad idea,
> Yes, and separate scripts for xdvi, dvips, kdvi, gdvi, texi2dvi? I
> don't think that this is a good approach.
Need it be scripts? Can't you just make a system call with the TEXMF shell
variable prepended, i.e.
TEXMF=blah
> We explicitly put the version number in, to prevent lilypond from
>
[EMAIL PROTECTED] writes:
> I just ran into trouble, because I upgraded my tetex installation in the
> middle of a session, and the new installation had different paths. Since
> TEXMF was set as an environment variable by lilypond, when I tried to run
> latex afterwards it didn't have the right pa
I just ran into trouble, because I upgraded my tetex installation in the
middle of a session, and the new installation had different paths. Since
TEXMF was set as an environment variable by lilypond, when I tried to run
latex afterwards it didn't have the right paths.
I suggest that lilypond shou
