debian packaging instructions
merged into debian/control fields since we are supposed to properly package our own projects
renaming from manage.py, not really installable that way
a bare simple init script, needs fixing and tweaking, not really used yet
renaming from manage.py, not really installable that way
missing from the setup.py calls
if we do have a settings file then why it is just an example anyway? we should be using it after installing the package IMHO, and if we did not want defaults to be shipped we should provide them in some other form
new setup script to be used by debhelper
apache config for a new sites-available
lintian cosmetics fixes
default log dir
packages user handling
i honestly do not understand why we should explicitely require a single version of modules, instead of relying on the ones supported by the distro (if they are old, we can update them, this would be fine)... in case it breaks later we will have to fix it with the right versions anyway, either from trusty or from utopic