Re: Which Linux distro for Lilypond

[Urs Liska]

Am 07.01.2017 um 09:59 schrieb David Kastrup:
> "H. S. Teoh" <address@hidden> writes:
>
>> On Thu, Jan 05, 2017 at 10:36:02AM +0000, Dr Nicholas Bailey wrote:
>>> Watch out for Debian. There isn't a Lilypond in Testing (Stretch)
>>> AFAIK. It's because they've removed the old scheme version. I develop
>>> in Testing in the hope that by the time I get around to releasing
>>> anything, it will be compatible with Stable :) Stable released rather
>>> infrequently, but I use it on our servers and it is very, well,
>>> *stable*.
>>>
>>> It's easy to install the Stable lilypond debian package on a Testing
>>> Debian box, fortunately. Debian is my favourite distro: I've tried
>>> others but always returned. Shame about the scheme thing, but it will
>>> sort itself out sooner or later (if it hasn't already!). I guess the
>>> clue's in the distribution name: "Testing" ;)
>> [...]
>>
>> I've been able to get Lilypond 2.19 to work in Debian/testing by
>> compiling from source (lilypond git HEAD) with `./configure
>> --enable-guile2`.  There are some Scheme-related deprecation warning
>> messages that show up while lilypond is running, but otherwise it seems
>> to be working just fine.
> If you never use a non-ASCII character and are satisfied with the speed
> of LilyPond dropping to less than a third and its memory requirements
> rising.
>
> This is not a viable option for serious work.
>

Unfortunately I ran into this very issue, changing from Debian stable
(in the Linux Mint Debian Edition incarnation) to vanilla Debian
testing. I did this because the PyQt5 packages in stable are too old to
run current Frescobaldi from its Git repository.
Now that I managed to get Frescobaldi running again I can't build
LilyPond anymore because in Debian testing I don't have guile 1.8
anymore :-(

For working *with* LilyPond it's not much of an issue to use the
releases, but I can't work *on* LilyPond right now ...

Urs

-- 
address@hidden
https://openlilylib.org
http://lilypondblog.org