51661c33a5
Sourcing of environment files is a bit different than running scripts, because they are imported into the current environment. That means that if they are fiddling with "set -x" you can get odd things in the output -- for example, if one environment file enables tracing then all proceeding sourcing will have it on, but all the files sourced before will not have output. This is super confusing. It's also very helpful to see how things are being expanded as they set environment variables. Thus I think the best idea is for environment files to leave tracing alone and dib-run-parts can a) give a useful output about what file it is sourcing and b) enable tracing around the import, then restore it to the previous state afterwards. Change-Id: I29f7df1514aeb988222d1094e8269eddb485c2a0 |
||
---|---|---|
bin | ||
tests | ||
.gitignore | ||
.gitreview | ||
LICENSE | ||
README.md | ||
setup.cfg | ||
setup.py | ||
tox.ini |
README.md
Standalone tools related to diskimage-builder
These tools were originally part of the diskimage-builder project, but they have uses outside of that project as well. Because disk space is at a premium in base cloud images, pulling in all of diskimage-builder and its dependencies just to use something like dib-run-parts is not desirable. This project allows consumers to use the tools while pulling in only one small package with few/no additional dependencies.