http://www.kde-look.org/content/show.php?content=10605 Reproducible: Always Steps to Reproduce: N/A Actual Results:
Created attachment 25613 [details] ebuild and associated files
If you're using this ebuild, put it in /usr/local/portage, or whatever overlay directory you use. DO NOT copy it over the existing portage location.
It turns out you'll have to download the alloy 0.5 tarball directly from the server, then move it to /usr/portage/distfiles. Additionally, the ebuild is masked, so ACCEPT_KEYWORDS='~x86' must be used.
Created attachment 25636 [details] ebuild and associated files Changed ebuild to fetch-restricted Instructions: Extract in /usr/local/portage (or other overlay directory) as root ACCEPT_KEYWORDS='~x86' emerge -vp alloy
Maybe a duplicate bug of ID 22780 ? cf. http://bugs.gentoo.org/show_bug.cgi?id=22780
Technically, yes, but mine is more up-to-date. :)
*** Bug 22780 has been marked as a duplicate of this bug. ***
in cvs