Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
lilypond: allow building on Darwin #79040
Motivation for this change
LilyPond was marked broken on Darwin in commit 287ab73. I’m not sure what’s changed, but I tried building it on my macOS 10.14 (Mojave) machine just now and it built and ran without a problem.
Ah, I see. I can reproduce locally the failures with lilypond-unstable and lilypond-with-fonts. I think it would make sense to at least mark lilypond itself as not broken. I’ve changed the PR so that it unmarks lilypond as broken on Darwin but leaves lilypond-unstable marked broken.
It also makes sense to me to use lilypond, not lilypond-unstable, as the basis of lilypond-with-fonts on Darwin. I’m not sure what to do about openlilylib-fonts, though. It depends on lilypond, but it doesn’t actually use LilyPond—it just uses that derivation’s version number to construct its own paths. Does it make sense for openlilylib-fonts to be its own top-level package? It seems to me like it might make more sense bundled into lilypond-with-fonts.