|
From: | Urs Liska |
Subject: | Re: Install LilyBoulez or other alternative fonts on Ubuntu |
Date: | Mon, 26 Jun 2017 14:22:21 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Am 26.06.2017 um 13:56 schrieb Urs
Liska:
Am 26.06.2017 um 13:42 schrieb Federico Bruni:_get_lilypond_font_path in config.py uses 'current'. Any chance to adapt it for distro installations? Well, I can rename it to "current" to make the script work...I'll have to look into the code once again, but it seems using "current" is definitely a stupid idea. So you shouldn't actually rename your installation folders ... But I think I should restructure the script anyway, since the non-local option doesn't work anymore anyway (since the fonts aren't at fonts.openlilylib.org anymore). Urs OK, I've misread your message and thought I had used "current" in the sense that I use it as the installation directory of my "current" LilyPond build. The problem is something different. The script checks if the given path points to a file (assuming it's the lilypond executable) or a directory (assuming an installation directory. What I did *not* consider is a "file" being a link or a wrapper script. I think /usr/bin/lilypond points to either a symlink or the wrapper script. Could you please give me the output of cat /usr/bin/lilypond ? From there the script goes up two levels and then goes down into the installation directory, looking for the font directories. In your case this results in a very confusing result because "share/lilypond/current" is the correct directory within an installation but looks very confusing prepended with /usr (= two levels above /usr/bin/lilypond). So apart from me fixing this in some way or another you should be good with $ sudo python install-lily-fonts -l -d /home/fede/.fonts -t /usr/share/lilypond/2.19.62 (i.e pointing to the installation directory) HTH Urs -- address@hidden https://openlilylib.org http://lilypondblog.org |
[Prev in Thread] | Current Thread | [Next in Thread] |