(unlurking, i didn't spend much time on lilypond recently)
On Mon, Oct 18, 2010 at 01:59:15AM +0100, Graham Percival wrote:
> > --) Two scripts still have "/usr/bin/python" lines
> > (python/auxiliar/manuals_definitions.py, and scripts/build/pytt.py).
> > Those should be changed to "@PYTHON@", right?
>
> python/ yes, since it's not something that people call manually.
> But stuff in scripts/build/ shouldn't have @PYTHON@, otherwise
> it'll bork if you call it manually.
But are those scripts supposed to be used without runnig autogen.sh
(and implied configure) first?
I may have some time during the next two weeks and arrange things
so those scripts will use the python detected by (or passed via
environment to) configure. If you want it.
> > Would it be feasible to use "#!/usr/bin/env @PYTHON@" or
> > "#!/usr/bin/env @TARGET_PYTHON@" for all Python scripts, using the
> > basename of the appropriate Python executable in place of the Make
> > variables?
#!/usr/bin/env YOUR_FAVORITE_INTERPRETER
should not be used ever. At least not for scripts that will be
installed system-wide. And if possible, not even for local scripts
(like scripts/build in lilypond).
Ciao,
Kili
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
