lilypond ebuild for latest stable release
Created attachment 18627 [details] lilypond-2.0.1.ebuild (Update) version bump plus one big change: The ebuild is now able to download and install pre-built type1 fonts. This is the default behavior. A buildpfa USE option is available for the masochistic.
Created attachment 18628 [details, diff] lilypond-2.0.1-coreutils-compat.patch
emerged fine with +buildpfa, but I compiled noteedit after it and noteedit gives me the following: $ noteedit LilyPond check: detection not possible TSE3 ALSA MIDI scheduler created $ lilypond -v lilypond (GNU LilyPond) 2.0.1 I think some more testing really needs to be done, and, if commited, this should stay at ~arch. LilyPond 2.0.1 in itself is working well for me- I did get it to export files beautifully, but it seems to mess up the noteedit gui on my system.
Thanks for the info, Jon. Have you tried the committed lilypond-2.0.0.ebuild with noteedit? Have you tried a manually installed 2.0.0 or 2.0.1 with noteedit? Thanks.
Hmm, I think my system is just quirky?! When I upgraded lilypond to 2.0.1, I was able to run noteedit fine, but then I recompiled noteedit (why, I'll never know) and it wouldn't work with 2.0.1 because of the previously mentioned error. I will try downgrading lilypond tomorrow and recompiling noteedit (again). Today I'm awefully busy. You'll have to excuse me- a nice girl my age needs me to go set up her network ;). additional info- $ noteedit -v Qt: 3.2.1 KDE: 3.1.4 NoteEdit: 2.3.2 $ gcc -v <snip> Thread model: posix gcc version 3.3.1 20030916 (Gentoo Linux 3.3.1-r4, propolice) CFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer -mfpmath=sse,387"
I took a peek at noteedit 2.3.2 and it is definitely not compatible with Lilypond 2.x. The problem with the detection process is that noteedit is looking for lilypond in the PATH, executing it with --version, and expecting something like "GNU LilyPond 2.0.1". Lilypond versions prior to 2.0 included a binary called "lilypond" and a python front-end called "ly2dvi". Because the python script is the primary interface, it has been renamed to "lilypond" in 2.x, and the binary formerly known as "lilypond" is now called "lilypond-bin". The python script now called lilypond returns a version string that is formatted differently ("lilypond (GNU LilyPond) 2.0.1") while lilypond-bin returns what noteedit expects. You can work around the detection problem by creating a symlink called lilypond which points to lilypond-bin. The symlink must be in front of /usr/bin/ in your PATH. Be aware that you would then have to call the script formerly known as ly2dvi by its full path, /usr/bin/lilypond. I tried this and it works, however I would be suspicious of other potential incompatibilities. For example, noteedit probably does not produce 2.x compliant .ly files (which you may be able to get around with convert-ly). Although I agree that this should be committed with ~arch, I'm confident that the noteedit compatibility issue is not a problem with this ebuild.
Very well put. And might I add that this is one of the better ebuilds that I've seen. I'll try the workaround mentioned, thanks for the tips! Should another bug be filed mentioning the incompatibility of noteedit with lilypond > 2.0?
Not here, but I'll send a report to the noteedit developers. Once a fixed version of noteedit is released, then we can work on getting it into portage.
noteedit-2.4.1 is out currently... and should be compatible with lilypond 2.x... I will be adding noteedit-2.4.1 and lilypond-2.0.2 to portage within the next week after my testing comes to an end...
noteedit-2.5.0 is in portage now... I'll test out lillypond next week-ish... unless raker has it ready...
2.0.3 is in portage.
