Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > Thomas Bushnell BSG schreef: > >> I'm distressed that nobody has bothered to fix the bug since then. In >> the thread on the mailing list you can see that if LILYPONDPREFIX is >> set correctly, the bug goes away. > > This issue has been addressed in a more robust manner in the 2.9 > series, and I would welcome a backport of the changes; we haven't > found the time to do it.
Good to hear. I think for Debian's purposes, setting LILYPONDPREFIX properly is probably the simplest solution. I look forward to 2.10 having a bettr fix in place. Thomas _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
