On Wed, Dec 12, 2012 at 3:02 PM, David Kastrup <d...@gnu.org> wrote: > Eric Pancer <epan...@gmail.com> writes: > >> On Wed, Dec 12, 2012 at 2:25 PM, David Kastrup <d...@gnu.org> wrote: >>> Which is pretty much what we are talking about. I was not talking about >>> /libexec but libexec, like the LilyPond executables are not in /bin but >>> some bin (well, actually out/bin) and, after installation, in some >>> /usr/local/bin (so the companion would be something like >>> /usr/local/libexec/lilypond/2.17.7/i686-pc-linux-gnu/ if we are taking >>> things literally). >> >> Okay, I understand that, but do not view LilyPond as a system utility. > > Which is why we are talking /usr/local/libexec rather than /usr/libexec > or /libexec.
Alright, it's your rodeo and I'm just a spectator. Just make sure you let us all know to add it to our PATHs since most people, I'm guessing, don't have /usr/local/libexec added. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
