openstack
/
requirements
Code Issues Proposed changes

README.rst: generate-constraints requires -r option 

It seems the requirements file must be specified when using the
generate-constraints utility.
This patch amends the README.rst file to reflect this, as it
currently appears to hint that the -r options default to
global-requirements.txt

Change-Id: I1b2d67f717e1050b11d974da69071b127dd864c8
This commit is contained in:
Salvatore Orlando 2015-08-14 04:00:32 -07:00
parent 2a6b64eeee
commit d8a9d65118
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.rst
View File

@ -153,7 +153,7 @@ Compile a constraints file showing the versions of resulting from installing
all of ``global-requirements.txt``::
generate-constraints -p /usr/bin/python2.7 -p /usr/bin/python3.4 \
-b blacklist.txt > new-constraints.txt
-b blacklist.txt -r global-requirements.txt > new-constraints.txt
edit-constraints
----------------
@ -184,12 +184,12 @@ Regenerating involves five steps.
2) Create a reference file (do this without your patch applied)::
generate-constraints -p /usr/bin/python2.7 -p /usr/bin/python3.4 \
-b blacklist.txt > baseline
-b blacklist.txt -r global-requirements.txt > baseline
3) Apply your patch and generate a new reference file::
generate-constraints -p /usr/bin/python2.7 -p /usr/bin/python3.4 \
-b blacklist.txt > updated
-b blacklist.txt -r global-requirements.txt > updated
4) Diff them::