On Tue, Nov 4, 2008 at 19:06:57 +0100, Adeodato Simó wrote: > (1) You should of course use python-central or python-support so that > the "xcbgen" Python package is always available for all installed > python versions. Hope that was your intention. :-) > Yeah, I think I got that working.
> (2) If you do that, then AFAICS no more meddling is strictly required for > things to work: the -p argument of c_client.py only appends the given > path to the list of directories Python searchs for modules. Since it > is appended at the end, the correct directory will be searched first. > That was the missing piece, thanks. > (3) The fact that xcb-proto.pc hardcodes a Python path is, uhm, bad. > xcb-proto instalation script should take care of installing the Python > files somewhere importable (e.g. the $prefix/lib/python2.5/... path > you mentioned), and assume the 'import xcbgen' statement in c_client.py > will work in any system with xcb-proto installed (the -p flag could > still be supported, that's orthogonal). > I'll sed the pythondir to /nonexistent in the .pc file, to avoid any problem with this. > Putting a Python path in the .pc file means xcb-proto has to be > recompiled whenever the default Python version changes. Maybe somebody > on the list can take care of educating upstream about this, if this > analysis is correct, which I believe it is. > > Was that clear enough? :-) > It was, thanks again! Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
