ff12a7954c
As in2a5fcfae02and in3e67e5c992using /usr/bin/env allows bash to be looked up in PATH rather than being hard-coded. As with the previous changes the same arguments apply - distributions have scripts to rewrite shebangs on installation and they know what locations to rely on. - For tests/compilation we should rather rely on the user to have setup there PATH correctly. In particular this makes testing from git easier on NixOS where do not provide /bin/bash to improve compose-ability.
33 lines
748 B
Bash
33 lines
748 B
Bash
#!/usr/bin/env bash
|
|
# -*- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; -*-
|
|
# ex: ts=8 sw=4 sts=4 et filetype=sh
|
|
|
|
COMMAND="$1"
|
|
KERNEL_VERSION="$2"
|
|
ENTRY_DIR_ABS="$3"
|
|
KERNEL_IMAGE="$4"
|
|
INITRD_OPTIONS_START="5"
|
|
|
|
if ! [[ $KERNEL_INSTALL_MACHINE_ID ]]; then
|
|
exit 0
|
|
fi
|
|
|
|
if [[ $COMMAND != add ]]; then
|
|
exit 0
|
|
fi
|
|
|
|
# If the boot dir exists (e.g. $ESP/<machine-id>),
|
|
# create the entry directory ($ESP/<machine-id>/<kernel-version>).
|
|
# This is the only function of this plugin.
|
|
MACHINE_ID_DIR="${ENTRY_DIR_ABS%/*}"
|
|
if ! [ -d "$MACHINE_ID_DIR" ]; then
|
|
exit 0
|
|
fi
|
|
|
|
if [ "$KERNEL_INSTALL_VERBOSE" -gt 0 ]; then
|
|
echo "+mkdir -v -p $ENTRY_DIR_ABS"
|
|
exec mkdir -v -p "$ENTRY_DIR_ABS"
|
|
else
|
|
exec mkdir -p "$ENTRY_DIR_ABS"
|
|
fi
|