opendev/bindep
Code Issues Proposed changes

Add dependency version examples to README

Browse Source 
The bindep README.rst lacked clarification on using version strings for dependency resolution.
Closes-Bug: #2000955

Change-Id: I92fb0af1a4ae751ec4dc90426a8c4beac6ce4e9f
Signed-off-by: Nick Shobe <nickshobe@gmail.com>
This commit is contained in:
Nick Shobe 2019-07-02 13:43:40 -05:00
parent 88850a55ec
commit e7ab6ac639
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README.rst
View File

@ -100,7 +100,8 @@ not work inside of the group.
Version constraints are a comma separated list of constraints where each
constraint is (== | < | <= | >= | > | !=) VERSION, and the constraints are ANDed
together (the same as pip requirements version constraints).
together (the same as pip requirements version constraints,
except that they require a space between the dep and version constraints).
Comments are allowed: everything from the first ``#`` to the end of the line is
ignored.
@ -170,6 +171,14 @@ This selects the ``ceph-common`` package when the profile ``ceph`` is
specified. However, it will only select the ``python-rbd`` package when both
``ceph`` and ``glance`` profiles are active.
To specify package versions::
python >=3.7,<=3.8
grep >=3.3
# OR with a platform profile
python [platform:brew] ==3.7.3
For a more comprehensive example check bindep.txt_ file that is used to
test bindep itself on multiple platforms.