Depend on the hackage vesion of xcb-types
make: don't format unless we /have/ to

Damn autopep8-ing things is slow.
fix connect(..., auth=...)

Closes #26
Be explicit about dependencies for pip installing

Closes #29
name right ubuntu xcb-render library in readme
autopep8 is not the default

The version in debian is painfully slow (even with parallel, I ran it for 5 CPU
minutes and it still didn't finish). If people want a formatted debug version
they can build one, but I'm not going to sit and wait for it :)
Add licensing clarification

Based on [1], noting "MIT" as the type of licence is ambiguous. In fact the
test of this license is the OSI approved Expat version of the MIT license, so
reflect that in the comment at the top.

[1]: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#license-specification
[2]: http://en.wikipedia.org/wiki/MIT_License#License_terms
Add a draft of debian/ directory
lintian fixes
Only complain if actually building xcffib

There are lots of other setup.py options, e.g. 'config' and such, so we don't
want to die on those, just when acutally building.
Change license to Apache 2.0

There are several reasons to do this, namely because it is similar in spirit to
MIT license, but it is What Everyone Else uses. The reason everyone else uses
it is because it contains a patent grant along with a grant to the rights of
the software. This doesn't apply in xcffib's case (I have no patents), but
there is existing infrastructure in place to understand and use Apache 2.0
licenses, where there is not for the pseudo-ambiguous MIT/Expat license (e.g.
Debian distributes a copy of Apache-2.0, but distributes no copy of any MIT
license).

Closes #30
fix another lintian error and run haskell tests