24d81ac061
OpenStack CI uses bindep to figure out which packages need to be installed on the host. However, when a bindep.txt file is not available, a default one is used which may or may not be good enough for all cases. It's best to have control over the packages which are going to be installed on the host and as such we add our own bindep.txt file. Change-Id: Idab36eb82d916183f2fb40d326d095c5a8ee34b2
15 lines
752 B
YAML
15 lines
752 B
YAML
---
|
|
other:
|
|
- bifrost host dependencies are now being installed using the
|
|
``bindep`` tool. New dependencies should be added to the bindep.txt
|
|
file with the appropriate profile information if necessary. Core
|
|
dependencies (ie those needed to bootstrap the system such as python,
|
|
gcc, libffi, etc) must be listed in both the bindep.txt file and the
|
|
scripts/install-deps.sh one for mainly two reasons. First of all, the
|
|
OpenStack CI may only consult the bindep.txt in order to pull the
|
|
necessary dependencies. Second, ``bindep`` needs certain packages to
|
|
be present in order to its dependencies to build properly.
|
|
|
|
More information about the ``bindep`` tool can be found at
|
|
https://docs.openstack.org/infra/bindep/
|