1.4 KiB
The requirements.txt and requirements_ansible.txt files are generated from requirements.in and requirements_ansible.in, respectively, using pip-tools
pip-compile
. The following commands should do this if ran inside the tower_tools container.
virtualenv /buildit
source /buildit/bin/activate
pip install pip-tools
pip install pip --upgrade
pip-compile requirements/requirements.in > requirements/requirements.txt
pip-compile requirements/requirements_ansible.in > requirements/requirements_ansible.txt
Known Issues
-
Remove the
-e
from packages of the form-e git+https://github.com...
in the generated.txt
. Failure to do so will result in a "bad" RPM and DEB due to thepip install
laying down a symbolic link with an absolute path from the virtualenv to the git repository that will differ from when the RPM and DEB are build to when the RPM and DEB are installed on a machine. By removing the-e
the symbolic egg link will not be created and all is well. -
As of
pip-tools
1.8.1
pip-compile
does not resolve packages specified using a git url. Thus, dependencies for things likedm.xmlsec.binding
do not get resolved and output torequirements.txt
. This means that:- can't use
pip install --no-deps
because other deps WILL be sucked in - all dependencies are NOT captured in our
.txt
files. This means you can't rely on the.txt
when gathering licenses.
- can't use