On Fri, Mar 27, 2009 at 06:51:28PM +0000, Cláudia Soares wrote: > > On 2009/03/27, at 14:43, Graham Percival wrote: > >> Claudia: if you could produce a patch for this, it would be great. >> Unfortunately, no action can be taken until/unless somebody can >> fix it. > > I'm not sure if I understood you well. > > Do you want a patch to change /usr/bin/python into /usr/bin/env python in > lilypond-book python script?
The source code for lilypond-book calls @target_pyt...@. During the cross-platform build process, this is replaced by the appropriate (or, in the case of OSX, **not** so appropriate) directory. If you can provide a patch to GUB (look at the Contributor's Guide) which changes the location for OSX, and if you can test that it works, then we'll accept the patch. Be warned that this is a very involved process; if you're experienced with cross-platform builds, I estimate it would take 10 hours. ... is it ideal that the build process is so complicated? No, not at all. Do we have an obvious alternative to switch to? No. If we /did/ have a clear alternative which was better, do we have the time to make the change in the next few months? Almost certainly not. :( So I'm afraid that this issue will remain unresolved. Sorry, - Graham _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
