Hello all,
Thank you all for all your effort in trying to keep LilyPond in Debian
9.0 "stretch" (the upcoming "stable") and for trying to migrate to
guile-2.0.
There are several packages, especially Frescobaldi, Denemo, Songwrite,
etc., that rely on LilyPond to work. Being a Debian maintainer of
Debian's frescobaldi package, a frequent user of Frescobaldi to
typeset music for my choir, and being the initial Debian's LilyPond
package maintainer from 1997-2004, I would be really sad to see
LilyPond disappear from Debian stable.
So, how about the following?
1. Include a local copy of guile-1.8 (multiple upstream tarballs)
in our LilyPond 1.18.2 packaging, probably compiling guile-1.8 statically
into so that a functional and stable LilyPond can stay in Debian.
2. [Optional] Create a new package called lilypond-1.19 (like gcc, golang)
or lilypond-development (like wine) to go into experimental (or
even unstable)
to test the guile-2.0 stuff.
I would be happy to do all the hands-on work, and provide the
necessary patches if successful, to make #1 happen before the Stretch
Freeze.
I would also like to help co-maintain the LilyPond package in the long
run to help share the workload.
What do you think? :-)
Thank you, and Cheers,
Anthony
