Hi! I bumped drivel-1.2.3.ebuild to drivel-1.3.0. It works for me. Adhering to the handbook, I am not attaching the ebuild. Is there a reason why we don't configure drivel with rhythmbox support? -Eddy Reproducible: Always Steps to Reproduce:
'The unstable, development release of Drivel 1.3.0...' as far as rhythmbox support goes.. guess it needs some USE, but it's another issue.
How about bumping the 1.2.3 ebuild to 1.2.4 in portage, which *is* the latest stable release?