The ebuild for denemo-0.8.2 doesn't create encodings.dir, fonts.dir and fonts.scale for Denemo's font. So I got the opportunity to update and fix it. It also adds a new dependency.
Created attachment 210324 [details] denemo-0.8.10.ebuild
At [1] 0.8.4 is "released" whereas the SF project page still says 0.8.12 is the latest (maybe stable) release. [1] http://ftp.gnu.org/gnu/denemo/
Created attachment 222231 [details] media-sound/denemo-0.8.10 updated ebuild Added missing dependencies, updated src_uri. I tried to adapt this ebuild to versions 0.8.12 and 0.8.14, both built but Denemo didn't work right, it only gave me a grey window.
The "gray window" problem described above seems to be due to a lilypond requirement. Not sure exactly why, but the problem appears without lilypond and goes away with lilypond. Also, fluidsynth is now supported and, again, seems to be required. If it's --enable-fluidsynth is NOT used, final linking will fail due to fluidsynth-related errors. I updated the ebuild with the following USE flags: doc +fluidsynth +lilypond fluidsynth and lilypond are forced on by default for the reasons listed above, and though this is not ideal, it works for me. I filed an upstream bug report regarding the fluidsynth issue, but not lilypond (that probably deserves more investigation).
Created attachment 225435 [details] media-sound/denemo-0.8.14.ebuild
Created attachment 225489 [details] media-sound/denemo-0.8.14.ebuild Installing LilyPond solved the "gray window" problem, thank you! Why are you letting the users try to build a not working denemo with USE flags? I suggest to remove that option. :)
(In reply to comment #6) > Why are you letting the users try to build a not working denemo with USE flags? > I suggest to remove that option. :) by default, the ebuild I provided does work. Users would have to intentionally disable the flags to make it not work. I chose to do it this way because these two items are *supposed* to be optional. Personally, I don't want/need either fluidsynth or lilypond support for how I use it, so if/when upstream fixes the bugs I plan on disabling those USE flags.
0.8.16 in portage
