Commit f20acd66d85 by Georges Racinet

INSTALL_HEPTAPOD: more precise pip instructions

biasing this very much against `pip hg+https` which has its
conter-intuitive quirks and is not upgrade friendly

--HG--
branch : heptapod
parent f231ddc2f56
......@@ -54,15 +54,33 @@ The Python packages to be taken from pypi.org are already listed alongside the
[Dockerfile](https://dev.heptapod.net/heptapod/heptapod-docker/blob/branch/default/heptapod/pip-requirements.txt),
just use that, but be sure to take it from the same tag as the sources.
Then install with pip from the following Mercurial URLs:
Then install from the following Mercurial URLs:
- https://mirror.octobus.net/heptapod/hg-git-heptapod
- https://mirror.octobus.net/octobus/hgext-loggingmod
- https://mirror.octobus.net/heptapod/py-heptapod
Note: `hgext_loggingmod` is an exception of the tagging policy.
After initial development, it just
stayed untouched, version 0.1.2 is fine.
For each one, rather to use `pip install hg+https`, which is quite error
prone, the simplest best way looks like this:
```
hg clone -u $TAG https://mirror.octobus.net/heptapod/py-heptapod
$PIP install -e py-heptapod
```
where `$PIP` is `pip --user` or `some/virtualenv/bin/pip` according to your
choice.
Notes:
- these repositories are small enough than pull exactly the wanted
revision is a needless complication.
- `hgext_loggingmod` is an exception of the tagging policy.
After initial development, it just stayed untouched, version 0.1.2 is fine.
- the `-e` flag will make your subsequent updates easier: you'll just have
to `hg pull -u NEW_TAG`, redo the `pip install -e` to account for package
metadata changes (notably entry points if any) and restart relevant processes.
### Configuration
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment