diskimage-builder/elements/dib-python/pre-install.d/01-dib-python

#!/bin/bash

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

python_path=$(command -v python2 || command -v python3)
if [ -z "$python_path" ]; then
    echo "Could not find python2 or python3 executable."
    exit 1
fi

ln -sf $python_path /usr/local/bin/dib-python
Add dib-python element Creating an element which we can use in #! lines to refer to either python2 or python3 depending on what it available. Change-Id: Ic47e18ad21c33ab9f0d11c04260a33725aeee814 2015-12-10 19:38:53 +00:00			`#!/bin/bash`

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

Run package-intalls with py3k if we must Use dib-python to run package-installs using the provided python version. Automatically detect the python version for our package-installs-squash since that runs outside the chroot. Change-Id: I926022bcf8cbcd81b051026ffd5d6477650045ad 2015-12-07 21:03:59 +00:00			`python_path=$(command -v python2 \|\| command -v python3)`
Add dib-python element Creating an element which we can use in #! lines to refer to either python2 or python3 depending on what it available. Change-Id: Ic47e18ad21c33ab9f0d11c04260a33725aeee814 2015-12-10 19:38:53 +00:00			`if [ -z "$python_path" ]; then`
			`echo "Could not find python2 or python3 executable."`
			`exit 1`
			`fi`

Force dib-python symlink creation The undercloud actually has dib run twice on it - once to create the instack image, and again when we run instack itself. The first run creates the dib-python symlink, and the second blows up because the link already exists. Force the link creation so the script is idempotent. Change-Id: I78f9e6f5afcf8ebe6d7911a7a434525ba7c737cf 2016-01-21 19:25:33 +00:00			`ln -sf $python_path /usr/local/bin/dib-python`