Am 26.06.2017 um 16:22 schrieb Federico Bruni: > > Unless I miss something, the problem is that GUB installers have > always usr/share/lilypond/current, while distro packagers (at least > Debian and Fedora for sure) prefer replacing it with the actual version. > > My guess is that you should change the script in a way that it can run > lilypond to find the version installed and then the correct path for > that installation. > > GUB changes some version to current here: > https://github.com/gperciva/gub/blob/master/gub/specs/lilypond.py#L120 > > It was not an happy decision as you may guess from the comment: > # WTF, current >
OK, now I start to see how that works. Maybe. So, what is the content (tree) of /usr/share/lilypond/2.19.62 in your installation? (I can't really test it because on my Debian 9 there still is not installation candidate for lilypond available.) Urs -- u...@openlilylib.org https://openlilylib.org http://lilypondblog.org _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
