Bug#951801: User setting of LILYPOND_DATADIR is not honoured

2020-02-23 Thread Simon Tatham
Don Armstrong wrote: > Could you try changing /usr/bin/lilypond to be this instead: > > #!/bin/sh > export LD_LIBRARY_PATH="/usr/lib/x86_64-linux-gnu/lilypond/2.18.2/guile" > exec "lilypond.real" "$@" > > and see if that works better? No, I'm afraid not. That was the first thing I tried too, in

Bug#951801: User setting of LILYPOND_DATADIR is not honoured

2020-02-22 Thread Don Armstrong
On Fri, 21 Feb 2020, Simon Tatham wrote: > However, the override doesn't actually work! [...] > In order to work around this, I tried to 'exec' the Lilypond binary > with an argv[0] that does not appear on PATH at all, which inhibits > the initial 'relocate' operation and causes the input value

Bug#951801: User setting of LILYPOND_DATADIR is not honoured

2020-02-21 Thread Simon Tatham
Package: lilypond Version: 2.19.81+really-2.18.2-13 The Lilypond documentation says that if you set the environment variable LILYPOND_DATADIR to point at a directory, then Lilypond will look for its data files (fonts, startup files etc) in that directory instead of /usr/share/lilypond/. In particu