On Sun, Nov 27, 2011 at 05:32:08PM -0600, DJ Lucas wrote: > I had xcb and xcb-utils working with Python3, but I figure > we'll be best to stick with Python2 until upstream wants the newer > version. Nothing needed or wanted Python3 as of last month until I made > it want Python3. >
For xcb, I was wondering about the xcb-util changes rather than Python. I've just managed to connect to fedora - they're still on xcb-util-0.3.6 (and they usually stay close to the bleeding edge). PLD are on 0.3.8 with xcb-util-image-0.3.8 with a note in the -util specfile that various parts have been split and are 'specs pending'. Language like that makes me think the're either hard or unnecessary. At freedesktop.org I can see -keysyms and -renderutil : all 0.3.8 variants were released near the end of April, I noticed a question from a packager in the xorg list archives which didn't seem to get any response. Haven't looked at debian-unstable (sometimes *more* bleeding edge, and occasionally broken in use as a result). I'm wimping out and staying with 0.3.6 unless someone shines light on this. For libxcb, fedora have a patch to add a pkgconfig file for pthread-stubs so that apps will link to that. But then, PLD have a longwinded sed to build without graphviz which isn't needed, and note that it depends on check (presumably, 'can use, to run hte testsuite, rather than 'requires'). Meanwhile, MesaLib is now at 7.11.2. I've gone back to using mesa-demos after 'patch' didn't think your patch applied (a couple of versions ago). ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
