More on xpra

My ticket (#79) on the xpra trac was closed as INVALID (a status which annoys me, because it fails to reflect sufficient granularity in why a ticket was closed). Boo.

The comment from Antoine was that xpra should be installed system-wide, in which case no funky

sys.path.insert(..)

is required. That’s true, and a great thing indeed. However, if you do not have root on the box(es) you want to run xpra on, you do need to futz around with sys.path, or you need to write a wrapper script which sets up PYTHONPATH for you. This is exactly the situation I found myself in earlier today, when I made xpra available on our network via an installation in my homedir.

Now that I’ve got that off my chest, it’s time to turn to the problem of the two shared objects which are part of the distribution. I’d like to make xpra available as a blended (in IPS terms) package. That means we need to have some way of putting

xpra/wait_for_x_server.so

and

wimpiggy/lowlevel/bindings.so

under $MACH. Guess I’ll be learning something about Cython and distutils.