Bye bye cmake

Since actions speak louder than words, I figured I'd show you what I mean when I recommended you guys ditch cmake. I'm sending this to you mainly for you to yell at me and tell me about all the things you don't like, and I'll do my best to explain why I think they make sense.

What I have in mind is a pretty much completely self-contained package that installs easily from the package index.

A few comments:

* You may notice that I've brought in a submodule `bpl-subset`. This contains just enough of Boost Python to build Python modules. I use it in just about all my Python modules, and so far it works well for me. As of right now, it does not contain UBlas, but making a derivative version with UBlas should be easy enough, if required, pending the outcome of issue #5. [Upstream](/inducer/bpl-subset)
* I've also brought in a file `aksetup_helper.py`, which brings in a simple configuration system, controlled by a file `siteconf.py` in the package directory, or a user-global file `~/.aksetup-defaults.py`. [Upstream](/inducer/aksetup).
* I've moved the pyviennacl Python source to the top level. You may hate this, but it's convention in Python packaging, and it makes 'python setup.py develop' work.

Anyhow, my main intention is to get the debate started. Outside of the Ublas issue above, this code is self-contained (i.e. not outside dependencies) and builds a working pyviennacl for me.