diskimage-builder/diskimage_builder/elements/dpkg/finalise.d/99-clean-up-cache

#!/bin/bash
# Do an apt-get clean. This will free some space.

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

if [ "${DIB_DISABLE_APT_CLEANUP:-0}" != "1" ]; then
    apt-get clean
fi
Revert "Cleanup apt cache after grub install" This calls chroot as a non-root user, which will always fail with EPERM. This reverts commit ab2d1a31f2177b26aada075201712b0061a1b771. Change-Id: Ie674fef694ad66e1ebc22083dec2a0bc34371e7b 2014-07-24 01:56:35 +00:00			`#!/bin/bash`
			`# Do an apt-get clean. This will free some space.`

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`
Revert "Cleanup apt cache after grub install" This calls chroot as a non-root user, which will always fail with EPERM. This reverts commit ab2d1a31f2177b26aada075201712b0061a1b771. Change-Id: Ie674fef694ad66e1ebc22083dec2a0bc34371e7b 2014-07-24 01:56:35 +00:00			`set -eu`
			`set -o pipefail`

Allow disabling apt-get clean Sometimes users want to maintain the apt cache in their images. Change-Id: Id49a04896cf3eeaf1557f1d644e4d8ba64716392 2015-03-04 23:38:52 +00:00			`if [ "${DIB_DISABLE_APT_CLEANUP:-0}" != "1" ]; then`
			`apt-get clean`
			`fi`