The developer of xmms-compress decided to create a command-line tool to work just like the xmms plugin did. Now both are in the package AudioCompress so I guess this ebuild should probably go in media-sound than media-plugins. The ebuild for the latest version and the digest are attached.
Created attachment 12015 [details] AudioCompress-1.3.ebuild
Created attachment 12016 [details] digest-AudioCompress-1.3
Created attachment 12017 [details] Manifest
if [ -n "`use xmms`" ];then emake || die else emake AudioCompress fi Do you really mean to never make both? Could someone want the commandline AudioCompress but not the xmms plugin? Would: if [ -n "`use xmms`" ];then emake || die fi emake AudioCompress be better?
Well actually AudioCompress is not dependent to xmms so it could be used as well with other programs. There is an example of its use with mpg123 on the site. So someone who doesn't use xmms could choose to not compile the plugin. The change in the ebuild that you propose should work as well but why would you want to run 'make AudioCompress' after you had run 'make' which also compiles AudioCompress? I don't quite understand the point in that change. I'm still learning in every ebuild I write how to make correct use of the USE flags so forgive my ignorance :-) Another thing that came to my mind is that DEPEND should be changed so that AudioCompress could be emerged even if xmms isn't.
I'll add this shortly
added. thanks for submitting it :)