Am 07.01.2017 um 10:20 schrieb Werner LEMBERG: >> 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 ... > Mhmm, compiling and installing guile 1.8 is not rocket science...
Probably not, but ... > Have you tried that already? ... i am not familiar enough with all this packaging stuff to be confident about installing alternative versions to system installed packages ... Where would I find suitable documentation or tutorials to do so (doesn't have to be explicitly about Guile 1.8 vs. 2 of course)? URs > > Maybe we have to bite the bullet and distribute guile 1.8 together > with lilypond. I know that this is a step into the wrong direction > since it doesn't force the guile maintainers to improve guile 2.x so > that lilypond can use it... > > > Werner -- 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
