add setup script for dependencies

[ischneider]

This will make it easier to setup a development environment and allow tracking dependencies (in git) as they arise instead of documenting them.

There are two types of external dependencies:

1. we don't/won't develop
2. we want to develop with (gsconfig, for example)

Other tools or means of managing deps don't/won't work well alone:

• virtualenv doesn't like it will work since the python home is set in qgis. additionally, another step would be required to collect the libraries
• pip/easy_install to local/global location has the same issue as virtualenv (collecting libraries)
• pip + requirements only works for -e dependencies (from git/svn/etc)

(I'd love to be wrong, BTW)

First type

Installed like this (this will install nose-html into the src/opengeo/ext_libs directory):

PYTHONPATH=src/opengeo/ext_libs  easy_install -a -d src/opengeo/ext_libs nose-html

We'd maintain a list of these in some file and run this command on all of them.

Second type

These can be managed with pip install -e URL or pip install -r and a requirements file.

Testing dependencies

These can be in a separate list of files and just filtered out in the packaging step.

Wrapping up installation

One idea would be to paver to wrap this and other tasks (install.py and package.py).

The different targets could include:

• setup - install dependencies
• install - copy/link files to appropriate plugin location
• package - create package for plugin (does not contain tests or dependencies)

[ischneider]

The paver script covers this for now.