openstack/barbican
Code Issues Proposed changes
b833108d5d
barbican/doc/source/contributor/dependencies.rst
Andreas Jaeger b86d6b5660 move documentation into the new standard layout 
This change moves existing files.
It is not meant to be the final word on how the main page looks or how the
other files are organized, but it gets everything roughly into shape. If
the barbican team wants to make changes, please do those as follow-up patches.

Note this does not touch the api directory, this one needs to be
migrated to the api-ref.

This is part of the docs migration work for Pike.

Change-Id: Ibb9d971806964ac185882272514ee9563089d69d
2017-06-30 20:12:52 +02:00

1.1 KiB
Raw Blame History

Adding/Updating Dependencies

Adding new Dependency

If you need to add a new dependency to Barbican, you must edit a few things:

  1. Add the package name (and minimum version if applicable) to the requirements.txt file in the root directory.

    Note

    All dependencies and their version specifiers must come from the OpenStack global requirements repository.

  2. We support deployment on CentOS 6.4, so you should check CentOS + EPEL 6 yum repos to figure out the name of the rpm package that provides the package you're adding. Add this package name as a dependency in rpmbuild/SPECS/barbican.spec.

  3. If there is no package available in CentOS or EPEL, or if the latest available package's version is lower than the minimum required version we must build an rpm for it ourselves. Add a line to rpmbuild/package_dependencies.sh so that jenkins will build an rpm using fpm and upload it to the cloudkeep yum repo.