• StoryBuild2

Package Xpra

Status: in progress

Create a Debian package for Xpra. The changes made in X11Selections make Xpra depend on the code from X11ProxySpike, so that will need to be packaged too and given a proper name.

Naming

The proper name for X11ProxySpike will be "xjack", which is a multi-way pun. It is starting off as a "jack of all trades", being an X protocol monitor and an X client library. It could be given a backronym where "-ck" stands for "connection kit" (not to be confused with the Jack Audio Connection Kit). Lastly, "jack" means 11 in cards, as in X11.

Tasks

• Merge the changes in x11-proxy's branch of plash.comms into trunk -- merged 716 and 717

• Package x11-proxy

  • Create Debian packaging and a setup.py

  • Move all the modules into a top-level package, xjack

  • Move into trunk in SVN
  • Remove branched copy of plash.comms

  • Add to list of packages to be built by BuildTools

• Package Xpra

• Split Python code out of "plash" package into a separate "python-plash" package, so that xjack will be usable without installing plash.
  • I was considering splitting only plash.comms into a separate package. This would involve changing the module names around again, to make plash.comms into a top-level package such as plash_comms.

  • Make sure that it's still easy to do development without reinstalling the Python code. Change BuildTools so that they will set up PYTHONPATH.

  • What happens to the run-uninstalled.sh script? It remains but doesn't set PYTHONPATH to point to the plash module.
  • Plash's Python C module (plash_core) would remain in the plash package.