Made some changes to the README.md to better install
Updated to reflect the reality of how to reliably install development anchor on Linux and OSX today. PBR was doing strange things the other way. Change-Id: I4284940fc9a528ed148e3965a61eaa5159a805b3 co-authored-by: Shellee Arnold <Shellee.Arnold@hp.com>
This commit is contained in:
parent
1e4684f4f5
commit
87aa484394
14
README.md
14
README.md
@ -38,19 +38,11 @@ to be present:
|
||||
* libssl (dev)
|
||||
|
||||
When everything is in place, Anchor can be installed in one of three ways. For
|
||||
development, run:
|
||||
development with virtualenv, run:
|
||||
|
||||
virtualenv .venv
|
||||
. .venv/bin/activate
|
||||
pip install -r requirements.txt
|
||||
python setup.py develop
|
||||
|
||||
For installing into virtualenv, run:
|
||||
|
||||
virtualenv path/to/environment
|
||||
. path/to/environment/bin/activate
|
||||
pip install -r requirements.txt
|
||||
python setup.py install
|
||||
source .venv/bin/activate
|
||||
pip install .
|
||||
|
||||
For installing in production, either install a perpared system package, or
|
||||
install globally in the system:
|
||||
|
Loading…
x
Reference in New Issue
Block a user