Mats Bengtsson <[EMAIL PROTECTED]> writes: > Since I will keep setting a link lilypond to point to the > current build-dir and I'd prefer to get all settings correct > by just changing this single link,
Yes. I had that setup too, and I thought it sucked, because you can't run 1.4 and 1.5 alongside eachother. Of course, you should use what you like best, but it would be good if the advertised build-dir solution that come with lily, work too. > I'd actually prefer if the > directory was <build-dir>/share/lilypond/, i.e. with no > version specific path name except for the build directory > itself. But that's not convenient, because you *have* to set LILYPONDPREFIX. If you include the version, it's very convenient to have lily's datadir point to the right place, so the executable will work from any terminal. That's handy if you run different lily versions all the time. The datadir includes the version, for reasons below. > Did you have any special reason to add that extra > directory level? Yes, it's the more standard thing to do if you want to support different versions to be installed. Having /usr/[local/]share/lilypond/<version> enables you to install and run several /usr/bin/lilypond-<version> alongside eachother. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org _______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
