Hi, On Fri, 9 Dec 2005, Johannes Schindelin wrote:
> On Thu, 8 Dec 2005, Matthias Neeracher wrote: > > > > > On Dec 8, 2005, at 10:26 AM, [EMAIL PROTECTED] wrote: > > > From: Johannes Schindelin <[EMAIL PROTECTED]> > > > > > > On Wed, 7 Dec 2005, Graham Percival wrote: > > > > > > > I don't understand most of these patch, > > > > > > I'll try to explain: > > > > > > > > pathsettings: > > > > > @echo export PATH=$(PATH) > > > > > + @echo export LILYPOND_DATADIR=$(LILYPONDPREFIX) > > > > > @echo export LILYPONDPREFIX=$(LILYPONDPREFIX) > > > > > @echo export PYTHONPATH=$(PYTHONPATH) > > > > > > This is needed so that lilypond does not try to use > > > /usr/local/share/something, but the files from where lilypond is compiled. > > > > That makes it definitely unsuitable for general purpose distribution. This > > location can be overridden at runtime anyway, can't it? > > Sorry, this *is* an override. Namely, to make the documentation even if > you have a lilypond installed which is an earlier version, and want to > "make" the user documentation. I think this very definitely should go in. > It fixes a bug. Call me an idiot! I retested it, and of course it does not fix a bug. There is no bug. It was just that I edited the wrong file in some debugging spree, and during the hunt for *that* error, I "fixed" LILYPOND_DATADIR. Sorry for the noise, Dscho _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
