It works to rename the current 2.1.0 ebuild to 2.2.0--it would be nice to get the version bump into portage. ;-) There are some flags that configure no longer recognizes (if it ever did) though, that should probably be looked at: * QA Notice: Unrecognized configure options: * * configure: WARNING: unrecognized options: --enable-readline, --enable-break, --enable-hints, --enable-asm, --enable-cursorblk, --enable-led, --enable-displayled, --enable-sndclip, --enable-linuxjoy Reproducible: Always
http://dev.gentoo.org/~mr_bones_/kitten_0day.jpg
Well, I can't help but be excited about this revbump, it's been two years since the last one. ;-)
I hacked the 2.1.0 ebuild to build 2.2.0 on my amd64 system and the sound is not working correctly. The same ebuild on my x86 system used to build 2.2.0 produces working sound. It may something weird with my amd64 system because I seem to remember 2.1.0 working correctly in the past but now it doesn't either. 2.0.0 does produce working sound for me on amd64.
I had problems with sound on 2.1.0 on my x86 machine, and I couldn't get sound to work with it no matter what I tried. It was the only application that didn't have sound. Also, even though there is sound now in 2.2.0, it's not correct; low volumes don't sound and high volumes sound like they're missing something. Vague, I know, sorry. :-P
2.2.1 is out now, and renaming the ebuild works perfectly. I should note that sound works perfectly on my desktop machine but is wonky on my laptop. Both are x86. If I can figure out what the difference between them that's causing the problem is, I'll report it here. :-)
2.2.1 is in portage.
Thank you! \o/
