diskimage-builder/diskimage_builder/elements/yum/pre-install.d/01-yum-keepcache

#!/bin/bash

if [ ${DIB_DEBUG_TRACE:-0} -gt 0 ]; then
    set -x
fi
set -eu
set -o pipefail

if [[ ${YUM} == "dnf" ]]; then
    # dnf is slightly different; doesn't have these by default
    cfg=/etc/dnf/dnf.conf
    echo "keepcache=1" >> $cfg
    echo "cachedir=/tmp/yum" >> $cfg
else
    cfg=/etc/yum.conf
    sed -i 's/keepcache=0/keepcache=1/' $cfg
    sed -i 's/cachedir=\/var\/cache\/yum/cachedir=\/tmp\/yum/' $cfg
fi
Add yum element. The yum element provides for specific customizations for yum based distros. The included customization is a yum cache mounted outside of the chroot so that yum downloaded packages are reused on subsequent image builds. Change-Id: I6833c9fdbc83cb09debec6a789082e105c917800 2013-07-31 13:37:57 +00:00			`#!/bin/bash`

Standarise tracing for scripts There is a wide variety of tracing options through the various shell scripts. Some use "set -eux", others explicity set xtrace and others do nothing. There is a "-x" option to bin/disk-image-create but it doesn't flow down to the many scripts it calls. This adds a global integer variable set by disk-image-create DIB_DEBUG_TRACE. All scripts have a stanza added to detect this and turn on tracing. Any other tracing methods are rolled into this. So the standard header is --- if [ "${DIB_DEBUG_TRACE:-0}" -gt 0 ]; then set -x fi set -eu set -o pipefail --- Multiple -x options can be specified to dib-create-image, which increases the value of DIB_DEBUG_TRACE. If script authors feel their script should only trace at higher levels, they should modify the "-gt" value. If they feel it should trace by default, they can modify the default value also. Changes to pachset 16 : scripts which currently trace themselves by default have retained this behaviour with DIB_DEBUG_TRACE defaulting to "1". This was done by running [1] on patch set 15. See the thread beginning at [2] dib-lint is also updated to look for the variable being matched. [1] https://gist.github.com/ianw/71bbda9e6acc74ccd0fd [2] http://lists.openstack.org/pipermail/openstack-dev/2014-November/051575.html Change-Id: I6c5a962260741dcf6f89da9a33b96372a719b7b0 2014-09-04 04:56:29 +00:00			`if [ ${DIB_DEBUG_TRACE:-0} -gt 0 ]; then`
			`set -x`
			`fi`
set -u and -o pipefail everywhere As with the previous similar changes, this is intended to catch problems as they happen instead of ignoring them and continuing on to potentially fail later. Setting this on all existing scripts will allow us to enforce use via Jenkins. Change-Id: Iad2d490c86dceab148ea9ab08f457c49a5d5352e 2014-04-03 02:24:15 +00:00			`set -eu`
			`set -o pipefail`
Add yum element. The yum element provides for specific customizations for yum based distros. The included customization is a yum cache mounted outside of the chroot so that yum downloaded packages are reused on subsequent image builds. Change-Id: I6833c9fdbc83cb09debec6a789082e105c917800 2013-07-31 13:37:57 +00:00
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-09-25 04:05:18 +00:00			`if [[ ${YUM} == "dnf" ]]; then`
Work around yum/dnf differences Some minor workarounds for Fedora >= 22 where dnf is the default package manager. The changes are documented on the Fedora release notes https://fedoraproject.org/wiki/Changes/ReplaceYumWithDNF Change-Id: I7d7d6f5d294980dcb217d6190a1efd9e0bbea9a6 2015-05-27 04:53:04 +00:00			`# dnf is slightly different; doesn't have these by default`
			`cfg=/etc/dnf/dnf.conf`
			`echo "keepcache=1" >> $cfg`
			`echo "cachedir=/tmp/yum" >> $cfg`
			`else`
			`cfg=/etc/yum.conf`
			`sed -i 's/keepcache=0/keepcache=1/' $cfg`
			`sed -i 's/cachedir=\/var\/cache\/yum/cachedir=\/tmp\/yum/' $cfg`
			`fi`