The "afterimage"-functionality for "x11-terms/rxvt-unicode" can be supplied by both, "media-libs/libafterimage" and "x11-wm/afterstep".* However, the RDEPEND of rxvt-unicode ebuilds just mentions libafterimage. This is a problem for afterstep-users, as libafterimage and afterstep block each other. So if one already has afterstep on the system and tries to emerge rxvt-unicode with afterimage portage aborts, whining about blocking packages… This applies to all rxvt-unicode ebuilds I came across. See "Expected Results" for proposed fix. * This is because Afterstep incorporates afterimage, libafterimage is merely the stand-alone version of it.) Reproducible: Always Steps to Reproduce: 1. emerge afterstep 2. emerge rxvt-unicode with USE=afterimage 3. Oh noes! Actual Results: Expected Results: Fix the ebuilds. The afterimage-related line of RDEPEND should look like this: "afterimage? ( || ( media-libs/afterimage x11-wm/afterstep ) )" Try doing this in /usr/portage/x11-terms/rxvt-unicode: sed -i 's/afterimage? ( media-libs\/libafterimage )/afterimage? ( || ( media-libs\/afterimage x11-wm\/afterstep ) )/g' *.ebuild
I'd say this would be better solved by pulling libAI out of AfterStep and using system libAI as a dependency. Solves several problems rather than just the rxvt-unicode one.
Good idea. It's fixed in all ebuilds.
Umm, guys, Now all the rxvt-unicode ebuilds has this line as RDEPEND: afterimage? ( || ( media-libs/afterimage x11-wm/afterstep ) ) But there is no media-libs/afterimage package in the tree. So it should be media-libs/libafterimage.
Damn you're right, reopened the bug, hope Jeroen will be seeing this soon. Paul, could you tell guys in #gentoo on freenode on this? I'm still banned because I tried to discuss about the "no dirty language" policy with one of the mods :/
fixed the dependency, thanks for spotting ;)
Thanks alot. :)
