The lilypond e-build pretty much the same as the current (2.2.6) ebuild, but it depends on another package called ec-fonts-mftraced, available from the lilypond website. But I'm not sure about the license on it. Also, it's kind of weird, because the make system isn't automake, and I'm new to ebuilds, so I hacked something together. Someone with more experience will have to check to see that I've done it in an acceptable manner. I also wasn't sure about what to do with the SRC_URI... it's set to the lilypond site right now. It seemed logical to put this in media-fonts, but I wasn't sure. Oh, and I'm not sure about the doc target... Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 43963 [details] lilypond-2.5.0 ebuild
Created attachment 43964 [details] ec-fonts-mftraced ebuild
The ec-fonts-mftraced ebuild is significant, because it is also the requirement of the stable lilypond version 2.4.x. Until now, we never had unstable builds of lilypond in the official tree.
And the 2.4.x ebuild should theoretically be the same as the 2.5.0 ebuild, as far as I can tell.
ec-fonts-mftraced and lilypond-2.5.2 are now in portage, thanks
Err, I get a """ GNU LilyPond 2.5.2 Processing `test2.ly' Parsing... warning: lily-guile: Must use #(set-paper-size .. ) within \paper { ... } Interpreting music... MIDI output to `test2.midi'... Track... Interpreting music... error: cannot find `feta20.afm' Music font has not been installed properly.Aborting """ Is it a problem with the ec-fonts-mftraced ebuild ?
I was able to get rid of that error by doing: source /usr/share/lilypond/2.5.2/buildscripts/out/lilypond-profile and then running lilypond. Presumably, there's supposed to be something in the ebuild to deal with this, as I see similar complaints for lilypond 1.6.? but I haven't encountered this with any of the lilypond ebuilds I've used.
Is this a problem with a build process or a problem with running lilypond after it has been built? If it's the latter, I believe it's normal behavior (i.e. you should be running ly2dvi and not lilypond directly). The e-build could certainly be modified to change this behaviour, though.
