Lets try debian/ back in trunk

[Jason Gerard DeRose]

Okay, as an upstream developer, I've always liked having debian/ in my tree because I like to build packages in my day to day testing... I feel it keeps my work more focused, makes sure I'm testing in a way that closely mirrors how my end users will use my software (via packages). Plus it's nice not to be spraying files around in /usr/local all wily nilly with `setup.py install`. Packaging is awesome, useful even for day-to-day upstream development.

But packagers don't like debian/ in the upstream tree, so this was changed during 0.1. rockstar moved debian/ into a separate branch and help me get a daily recipe working with a merge (thanks, Paul, you truly are a rockstar).

However, first thing I noticed is that this slowed me down, made things a bit more difficult to manage because I couldn't land a change in trunk and the corresponding needed change in debian/ (for the daily builds) all in one merge. As Paul said, eventually a package gets to a point where changes in debian/ are seldom, then it's not such a problem. But in 0.2 and 0.3 there will be a lot of tumult in debian/, so I'm going to move it back into trunk.

As a hopefully good compromise, I wont add debian/ in MANIFEST.in, so it still wont be in the release tarballs.

Note that I'm not trying to step on the toes of packagers. Once dmedia is officially in Debian/Ubuntu, I'll just use the official debian/ in my upstream work (with perhaps dependency changes as required). Anyone have thoughts on this?