On Sun, Mar 07, 2010 at 10:00:05AM +0100, Hans Aberg wrote: > On 7 Mar 2010, at 08:12, James Bailey wrote: > >> Currently, the instructions on getting LilyPond up and running in a >> terminal on mac osx have the user create a script which calls the >> lilypond application, and then add the location of the script to the >> $PATH. Is there any advantage of this over just having the user add >> the location of the lilypond binary to the $PATH? > > They are different: LilyPond.app/Contents/Resources/bin/ has other stuff > in it than just the lilypond programs, for example ps2pdf. If one adds > this location to the environment variable PATH, one must decide which > version of these to call.
I'd forgotten about this, thanks! > But one could add /usr/local/bin/ before the > Lilypond directory. In addition, I have paths to MacPorts /opt/, Fink > /sw/, and TeX-Live /usr/local/texlive/ TeX. > > LilyPond seems fairly up-to-date, so it might be added after before or > after MacPorts. If you rely on "seems fairly up-to-date", then any time there's a version clash, you could get serious problems. I think the shell script way is more reliable. Cheers, - Graham _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
