af565480e7
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have. |
||
---|---|---|
doc/source | ||
pbrx | ||
playbooks/container-images | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
babel.cfg | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
pbrx
Utilities for projects using pbr.
pbr is very opinionated about how things should be done. As a result, there are a set of actions that become easy to deal with generically for any pbr based project. pbrx is a collection of utilities that contain support for such actions.
Note
Each of the utilities has a primary focus of working for projects using pbr. However, some of them will also work just fine for non-pbr-based projects. When that is the case, the utility will be marked appropriately.
- Free software: Apache license
- Documentation: https://docs.openstack.org/pbrx/latest
- Source: https://git.openstack.org/cgit/openstack/pbrx
Features
Each utility is implemented as a subcommand on the pbrx
command.
- install-siblings
-
Updates an installation with local from-source versions of dependencies. For any dependency that the normal installation installed from pip/PyPI,
install-siblings
will look for an adjacent git repository that provides the same package. If one exists, the source version will be installed to replace the released version. This is done in such a way that any givenconstraints
will be honored and not get messed up by transitive depends. - build-images
-
Builds container images from a project's source tree. The
python:alpine
base image is used, and dependencies are taken frombindep.txt
for distro requirements andrequirements.txt
for python requirements. A base image is made for the project itself, and then an additional image based on the base image for every entry inentry_points.console_scripts
in thesetup.cfg
file.