Bug 198944 – >=x11-terms/rxvt-unicode-8.3 has automagic media-libs/libafterimage dependency

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Rafał Mużyło 2007-11-12 15:43:10 UTC]

rxvt-unicode since 8.3 can use libAfterImage =>1.15 for background/transparency.
I think this should be useflag controlled (not automagic).

[Comment 1 Jakub Moc (RETIRED) 2007-11-13 20:17:27 UTC]

*** Bug 199087 has been marked as a duplicate of this bug. ***

[Comment 2 pierre 2007-11-13 20:29:57 UTC]

The new 199087 was marked 'duplicate' to this one. That's very nice
except this was a "would be nice" while 199087 is a "doesn't work".
This is what I was saying:

x11-terms/rxvt-unicode-8.4: pixmap option disappeared, dependency missing?

/usr/bin/urxvt -pixmap '/path/to/background/image.xpm'
(version x11-terms/rxvt-unicode-8.4) now returns
urxvt: "pixmap": unknown or malformed option.
urxvt: "/path/to/background/image.xpm": malformed option.

Comparing the distributions for 8.4 and 8.3, this seems
to be because -pixmap now requires libAfterImage while in 8.3 libXpm
may have been enough:

configure.ac:  AC_DEFINE(XPM_BACKGROUND, 1, Define if you want to have
sexy-looking background pixmaps. Needs libXpm or libAfterImage)

has become in 8.4:

configure.ac:  AC_DEFINE(BG_IMAGE_FROM_FILE, 1, Define if you want to have
sexy-looking background pixmaps. Needs libAfterImage)

Meanwhile media-libs/libafterimage is not depended by the ebuild and
is masked anyway (don't know why, maybe just not used much).

That's as far as I got. Don't take it for granted that the difference
above is the problem and the entire problem.
I'll probably revert to 8.3 for now.

So, *if* that's the whole of the problem, libAfterImage is not just an
option anymore.

[Comment 3 Jakub Moc (RETIRED) 2008-01-15 09:37:57 UTC]

*** Bug 202514 has been marked as a duplicate of this bug. ***

[Comment 4 Jesse Luehrs 2008-05-08 16:49:57 UTC]

Created attachment 152493 [details]
modified 9.02-r1 ebuild

Here's a modification to the 9.02-r1 ebuild for this problem... I'd personally rank this issue as slightly more serious than 'nice to have', considering each terminal I open uses around 2mb of ram without libafterimage, but around 22mb of ram with.

[Comment 5 Jesús Guerrero Botella (RETIRED) 2008-05-08 16:50:44 UTC]

This should be addressed, the ram usage drops drastically when urxvt/urxvtd do not link against libafterimage. I can confirm it.

rxvt-unicode is working here (including the daemon) without a glitch with libafterimage disabled.

[Comment 6 Nick White 2008-05-09 16:28:07 UTC]

I also confirm the massive extra resources needed when using libafterimage - indeed on my comparitively low-spec system (1.2GHz, 512MB RAM), X became very unstable when any rxvt-unicode windows were open.

So yes, this is more than just a 'convenience' issue.

[Comment 7 René Nussbaumer (RETIRED) 2008-06-21 18:27:04 UTC]

This has been addressed in rxvt-unicode-9.05

[Comment 8 René Nussbaumer (RETIRED) 2008-06-21 18:32:29 UTC]

*** Bug 221835 has been marked as a duplicate of this bug. ***