Closed ischneider closed 10 years ago
looks good.
2 things:
a) I guess tests should not be packaged. b) dependencies must be packaged, except for those only required fo testing
@volaya
When I said 'tests and deps are packaged' I should have noted 'tests and their deps are packaged'.
Looking forward, I agree tests should not be packaged though I wasn't sure if for the moment clients would want them or not. This is as easy as adding an exclude entry in the options section.
Excluding the test deps is a little bit more work when using the current setup (where all deps are in the same directory) since the dep name and resulting egg file can be different (nose-html/nose_html) in addition to executables (nosetests, coverage). I attempted tackling this by adding to the excludes based on the contents of the requirements file (instead of having to hard-code the entries in the exclude options). Another approach would be to install test deps to a separate directory and add that site in the plugin if it exists.
requires pavement, run paver help to get commands.
note - changes external libraries directory to ext-libs to prevent python path confusion (since ext-libs is not a valid package directory)
also supports adding 'source' requirements - git checkouts, like for gsconfig
replaces the install.py and package.py scripts, too
currently all tests and deps are packaged though this could be adjusted