amarok-2.2_beta1 is out (known as amarok_2.1.180 in the tarball). More importantly, they aren't accepting bug reports for 2.1 any more, so we should add 2.2 asap. I tried using the current ebuild, with the following changes: - Rename ebuild to to amarok-2.1.180.ebuild - Change fetch url. s/stable/unstable but it failed to build. I don't have the time/experience to troubleshoot atm. If someone's writing an ebuild for this, will they have a think about why media-sound/amarok-utils exists? It looks as though it's the same ebuild as amarok, but with a one-line change. Surely BUILD_UTILITIES can be controlled by a USE flag, and we could just have a single ebuild. (Just a thought). Reproducible: Always
amarok-2.1.80 is already in the kde-testing overlay. http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=commit;h=b04a09fa5f499f58b603b81dc5cde2270f7787b3 As this is a beta release, I'll leave it in the overlay for now.
(In reply to comment #1) > amarok-2.1.80 is already in the kde-testing overlay. Awesome. My previous comment about amarok-utils stands however. I'll change the bug title to reflect. Longer version: It's a messy duplication of an ebuild, for a single flag. This should be handled by USE flags. (eg. USE=player -utilities)
(In reply to comment #2) > (In reply to comment #1) > > amarok-2.1.80 is already in the kde-testing overlay. > > Awesome. My previous comment about amarok-utils stands however. I'll change the > bug title to reflect. > > Longer version: > It's a messy duplication of an ebuild, for a single flag. This should be > handled by USE flags. (eg. USE=player -utilities) amarok has been split in amarok and amarok-utils. Your reasoning would also apply to all apps in each of the kde tarballs, but we've opted a long time to introduce them and recently to only support split ebuilds. Although I haven't splitted the ebuilds myself, I've been bumping them and it seems some people might be interested just in the utils.
(In reply to comment #3) > amarok has been split in amarok and amarok-utils. Your reasoning would also > apply to all apps in each of the kde tarballs, but we've opted a long time to > introduce them and recently to only support split ebuilds. > Although I haven't splitted the ebuilds myself, I've been bumping them and it > seems some people might be interested just in the utils. Ah - fiar enough. I didn't know that was how it worked. Still, the situation where someone only wanted amarok-utils and not amarok is covered by my example with USE="-player utilities"
I'm closing this bug as amarok-2.2 has been put in the tree (original purpose of the bug) and as we won't be merging the ebuilds again - therefore WONTFIX.