[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Packaging LilyPond after distribution moves to Guile 2 [was Re: intent b
From: |
Trevor Daniels |
Subject: |
Packaging LilyPond after distribution moves to Guile 2 [was Re: intent bug on line start] |
Date: |
Fri, 18 Aug 2017 17:35:03 +0100 |
----- Original Message -----
From: "David Kastrup" <address@hidden>
> I had recently upgraded my system to 64bit and now
> have been able to install the default Ubuntu 2.18.2. I was interested
> to see how they dealt with Guile no longer being in distribution.
>
> address@hidden:/tmp$ ldd /usr/bin/lilypond
> not a dynamic executable
> address@hidden:/tmp$ file /usr/bin/lilypond
> /usr/bin/lilypond: POSIX shell script, ASCII text executable
> address@hidden:/tmp$ cat /usr/bin/lilypond
> #!/bin/sh
> export LD_LIBRARY_PATH="/usr/lib/x86_64-linux-gnu/lilypond/2.18.2/guile"
> exec "/usr/bin/lilypond.real" "$@"
>
> O.K.
>
> Not bad at all. Maybe we should create some advice for packagers? This
> here is way better than "muddle through with the current Guile-2.0 state
> and let your users alone with the problems".
That does indeed seem quite elegant, and neatly solves
the problem caused by the move of the distribution to Guile-2.
Could we make a similar change to our own, i.e. LilyPond's, distributions?
Trevor
---
This email has been checked for viruses by AVG.
http://www.avg.com
Re: intent bug on line start, Phil Holmes, 2017/08/18