diskimage-builder/diskimage_builder/elements/package-installs/install.d/01-package-installs

#!/bin/bash

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

package-installs -d $(dirname $0)
package-installs-v2 --phase install.d /tmp/package-installs.json
Support declarative package installs/uninstalls Adds a new element, package-installs, that provides an interface for declarative package installs and uninstalls. Packages to install can be added to an install.d/package-installs-<element-name> file. The set of packages listed across such files are installed in a single transaction at the beginning of install.d. Prefacing the package name with a "-" indicates that the package should be uninstalled at the end of the install.d phase. Again, the full set of uninstalls are done in a single transaction. An element providing a package-installs file should add package-installs to its element-deps file. Change-Id: I5b540388eff1079c8dee933b869463371481152b 2014-04-24 20:51:24 +00:00			`#!/bin/bash`

Package installs defaults to tracing off There isn't a good reason we should be defaulting to trace on for these scripts. Change-Id: I1b9ac9388f51a49e6912d800914a0e0f2faec604 2015-12-20 00:03:51 +00:00			`if [ ${DIB_DEBUG_TRACE:-0} -gt 0 ]; then`
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			`set -x`
			`fi`
			`set -eu`
Support declarative package installs/uninstalls Adds a new element, package-installs, that provides an interface for declarative package installs and uninstalls. Packages to install can be added to an install.d/package-installs-<element-name> file. The set of packages listed across such files are installed in a single transaction at the beginning of install.d. Prefacing the package name with a "-" indicates that the package should be uninstalled at the end of the install.d phase. Again, the full set of uninstalls are done in a single transaction. An element providing a package-installs file should add package-installs to its element-deps file. Change-Id: I5b540388eff1079c8dee933b869463371481152b 2014-04-24 20:51:24 +00:00			`set -o pipefail`

package-installs for pre-install.d/post-install.d Packages are often also installed in both the pre-install.d and post-install.d phases. This patch expands the package-installs element to support declarative package support for these phases in addition to the existing support for install.d. The actual install/uninstall logic is moved to common scripts under bin/ so that it can be reused across the different phases. Change-Id: Id51d0bbad232737fc8b5ffaf016dec50cd5b66c9 2014-07-21 17:03:31 +00:00			`package-installs -d $(dirname $0)`
Rework package-installs to collapse on build host Instead of doing the work in the image of parsing through the element's package-install declarations, we can squash it on hostside, where we have both YAML and JSON available to us, and then emit a single pre-processed file into the target to be used later. Change-Id: I3f182aa3aae0a79b2f3ea4e66c1878ad12878b0a 2014-12-10 16:19:28 +00:00			`package-installs-v2 --phase install.d /tmp/package-installs.json`