Please bump x11-libs/cairo-1.8.6. It makes x11-wm/awesome users happy cause fixed memory leak in cairo-xcb.
http://git.overlays.gentoo.org/gitweb/?p=dev/loki_val.git;a=blob;f=x11-libs/cairo/cairo-1.8.6.ebuild;h=11b89fe8722a9c366c1d11da0d5020dde8c9dc41;hb=73e9fe7f37a9e86e18ee52144229ec674e9a2bfb Also fixes bug 247206 as described in the bug.
I'm actually considering disabling cairo-xcb since it's a lot less mature then the Xlib backend and has a bunch of issues as described by upstream.
That strikes me as a bad idea. For one thing x11-wm/awesome requires cairo built with xcb, so you'd have to remove it from portage. For another thing, it doesn't seem like any problems with the xcb backend will affect performance of any programs that don't specifically use it. If you find such a problem, for example if a memory leak or rendering problem in the xcb-backend affects programs that only use the xlib backend,then the proper course of action would be to make sure the xcb use flag is not enabled by default in the cairo ebuild, and make the ebuild spit out a warning during emerge if the use flag is enabled. Xcb is one of the more interesting of the experimental backends for cairo, and gentoo users should get a chance to test it if they want to. It will probably become officially supported relatively soon, but making it difficult for Gentoo users to try it out will not help that to happen. I for one would like to see if that memory leak is fixed in 1.8.6 as the poster of this bug suggested, so please let's bump this to the latest stable release (1.8.6) with the xcb use flag available, with or without an ewarn.
*cairo-1.8.6 (24 Dec 2008) 24 Dec 2008; Doug Goldstein <cardoe@gentoo.org> +cairo-1.8.6.ebuild: version bump. Fixes --as-needed issues. Fixes directfb issues. Fixes PDF/PS backend issues.
