On 2008/12/04 16:59 +0100, Werner LEMBERG wrote: > > Maybe it shouldn't be in buildscripts/, but I it definitely > > doesn't belong in scripts/ > > Then I suggest a new directory `auxscripts'. It would simplify > maintainance.
The only good reason for building most buildscripts is specifying a Python binary path at configure invocation different from the default Python binary when scripts are run, but this is might be a sufficient reason to keep current stuff in buildscripts. OTOH it was convenient for most users to just run the script in buildscripts without having to "make -C buildscripts" and call the script in out/. Maybe we could create a shell script called auxscript at top of the source tree #!/bin/bash make -C buildscripts export PYTHONPATH=buildscripts:$(PYTHONPATH) exec buildscripts/out/$@ It could be then called as auxscript makelsr LSRDIR auxscript check_translation FILE BTW this would simplify check_translation invocation on individual files. If there is not objection, I'll add this stuff. Cheers, John _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
