"Phil Holmes" <em...@philholmes.net> writes:
> I think we should do some sweeping up in cobwebby corners, if we can.
> In particular, when we can't find any reason for the code to be there
> in the first place. I've not worked out yet how to get git to show
> which commit put that code in. If someone could either do that, or
> explain how to, I think it could help.
git grep LILYPOND_RELOCATE_PREFIX
Documentation/misc/ChangeLog-2.10: * lily/main.cc (setup_paths): fix:
LILYPOND_RELOCATE_PREFIX.
Documentation/misc/ChangeLog-2.10: * lily/main.cc (setup_paths): read
LILYPOND_RELOCATE_PREFIX
lily/relocate.cc: if (getenv ("LILYPOND_RELOCATE_PREFIX"))
lily/relocate.cc: prefix_directory = getenv
("LILYPOND_RELOCATE_PREFIX");
git gui blame lily/relocate.cc
/RELOCATE_PREFIX
Click on line. There are some cases:
commit 38e0fd809d01de319d40224b5d2279888304b2d3
Author: Jan Nieuwenhuizen <jann...@gnu.org> Fri Feb 2 13:06:30 2007
Committer: Jan Nieuwenhuizen <jann...@gnu.org> Fri Feb 2 13:06:30 2007
Finish rename of LILYPONDPREFIX to LILYPOND_DATADIR. Remove confusion
between prefix (/usr) and lilypond_datadir (/usr/share/lilypond/x.y.x),
fixes running from compile prefix and build tree with `current' link.
commit 38e0fd809d01de319d40224b5d2279888304b2d3
Author: Jan Nieuwenhuizen <jann...@gnu.org> Fri Feb 2 13:06:30 2007
Committer: Jan Nieuwenhuizen <jann...@gnu.org> Fri Feb 2 13:06:30 2007
Finish rename of LILYPONDPREFIX to LILYPOND_DATADIR. Remove confusion
between prefix (/usr) and lilypond_datadir (/usr/share/lilypond/x.y.x),
fixes running from compile prefix and build tree with `current' link.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
