Merge lp:~allenap/txlongpoll/bootstrap-without-net into lp:txlongpoll
Status: | Merged |
---|---|
Approved by: | Gavin Panella |
Approved revision: | 84 |
Merged at revision: | 78 |
Proposed branch: | lp:~allenap/txlongpoll/bootstrap-without-net |
Merge into: | lp:txlongpoll |
Diff against target: |
252 lines (+107/-61) 4 files modified
Makefile (+59/-41) README (+35/-8) buildout.cfg (+12/-11) setup.py (+1/-1) |
To merge this branch: | bzr merge lp:~allenap/txlongpoll/bootstrap-without-net |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Raphaël Badin (community) | Approve | ||
Review via email: mp+81323@code.launchpad.net |
Commit message
Many changes related to improving deployment of txlongpoll as a working service.
Description of the change
Several fixes relating to making deployment easier for the LOSAs, and
reliably repeatable:
- Make txlongpoll bootstrappable locally, without network, and build
from cache.
- `make build` now only builds what's needed to _run_ txlongpoll.
- `make bin/test` installs the test runner and dependencies.
- `make tags TAGS` builds tag files.
- Build with relative paths to make deployment a bit easier, which
goes in hand with the next change...
- `make build-update-paths` is for the use of people deploying
txlongpoll, i.e. the LOSAs. They will build txlongpoll on one
machine and sync it to another, but at a different fs location.
`make build-update-paths` fixes the last few remaining absolute
paths in the buildout. I suspect that the need to do this indicates
a deficiency or bug in buildout or one of the recipes.
- Updated the README to reflect much of the above.
- Depend on txAMQP >= 0.5 because lower versions cause test failures.
Looks good.
[0]
146 +- Remove the --setup-source and --download-base options in Makefile to from-cache = true`` line in buildout.cfg
147 + allow bootstrap.py to download setuptools.
148 +
149 +- Comment out the ``install-
150 + to allow bin/buildout to download dependencies.
I wish it would be more straight forward to do this (like running make with a simple option) but I'm not sure it's feasible/simple.
[0]
47 +TAGS: bin/tags
48 + bin/tags --ctags-emacs
49 +
50 +
51 +tags: bin/tags
52 + bin/tags --ctags-vi
Just curious here, is this standard (the name of the targets I mean)?