On Tue, Jul 25, 2006 at 02:08:03AM -0700, Thomas Bushnell BSG wrote: > 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. > It doesn't work in 2.9 series, I have tested tomorrow. Actually, the only one solution that I found is to make an symbolic link of pythons scripts in python/ -> scripts/ When I did that, the bug seems to go away, and help2man seem to make correctly his job. There is a problem for scripts in scripts/ for finding files in python, and when I put them in the same directory, the problem goes away.
I think there is a problem again, the new implementation of LILYPONDPREFIX in 2.9 series doesn't seem to correct the problem. -- .---. Ludovic RESLINGER / \ [EMAIL PROTECTED]@./ Trumpet Student in CNR /`\_/`\ Free Software Developer // )X( \\ | \ : )|_ _,'| .''`. /`\_`> <_/ \ @======TTT=====::_ | : :' : \__/'---'\__/ ((_<=HHH___)) `.| `. `'` `---UUU---'=> `-
signature.asc
Description: Digital signature
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel