diskimage-builder

History

Ian Wienand b57714af75 Use $YUM instead of direct calls in more places A few places we either assume centos uses "yum" directly, or have switching based on the distro type. In both cases, we can use ${YUM} directly to avoid ambiguity Change-Id: I71095a9bd1862f8956b5982fbbb3e1d213926c14		2019-10-03 00:22:18 +00:00
..
bin	Merge branch 'master' into merge-branch	2017-02-09 13:35:53 +11:00
cleanup.d	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
extra-data.d	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
post-install.d	Use $YUM instead of direct calls in more places	2019-10-03 00:22:18 +00:00
pre-install.d	Use $YUM instead of direct calls in more places	2019-10-03 00:22:18 +00:00
root.d	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
element-deps	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
README.rst	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00

README.rst

===
yum
===
Provide yum specific image building glue.

RHEL/Fedora/CentOS and other yum based distributions need specific yum
customizations.

Customizations include caching of downloaded yum packages outside of the build
chroot so that they can be reused by subsequent image builds.  The cache
increases image building speed when building multiple images, especially on
slow connections.  This is more effective than using an HTTP proxy as a yum
cache since the same rpm from different mirrors is often requested.

Custom yum repository configurations can also be applied by defining
`DIB_YUM_REPO_CONF` to a space separated list of repo configuration files. The
files will be copied to /etc/yum.repos.d/ during the image build, and then
removed at the end of the build. Each repo file should be named differently to
avoid a filename collision.