* pr-188:
  Added splash
  Update hook.preset with (commented out) predefined values for UKIs

* pr-189:
  archlinux -> arch
  Remove UKIs as well when uninstalling kernel

* origin/github/fork/nl6720/shellcheck:
  lsinitcpio: use the image passed to analyze_image
  mkinitcpio: fix shellcheck issue in process_preset
  Improve bash syntax in mkinitcpio, lsinitcpio and functions
  use correct MODULES_DECOMPRESS in manpage

The `analyze_image` function should use the image file passed to it
instead of reading the global "$_image" variable itself.

Use bash nameref to have proper access to the preset-specific
`*_microcode` arrays.

Quote, quote and quote some more.

Most of the issues were found with shellcheck.

Co-authored-by: Isaac Good <IsaacG@users.noreply.github.com>

By Tobias Powalowski
* origin/merge-requests/193:
  use correct MODULES_DECOMPRESS in manpage

See merge request !193

* origin/merge-requests/192:
  add -p to fix reproducibilty

By Josephine Pfeiffer
* origin/merge-requests/191:
  made messages consistent

See merge request !191

By Sebastian Wiesner
* origin/merge-requests/185:
  Fix mkinitcpio check

See merge request !185

xz 5.4 changed the behaviour of `-T0` to always use "multithreaded mode",
even on single-core CPUs.
See https://git.tukaani.org/?p=xz.git;a=commitdiff;h=0adc13bfe32c14f3e4c6ce9f2d4fdf4112ab53f4

This means that xz output when using `-T0` should now be reproducible.

* pr-182:
  Detecting the size of unified kernel image sections automatically

Arranges all objcopy arguments into OBJCOPYARGS. The checks are also
rearranged by the order of appearance in the unified kernel image.  The
hardcoded VMA addresses are removed and the section sizes are detected
automatically. This allows arbitrary sized kernel images to be used.

See discussion on [GitHub](https://github.com/archlinuxarm/PKGBUILDs/pull/1910).

Fixes #133.

According to kernel-install(8) the initrd_generator setting ends up
in $KERNEL_INSTALL_INITRD_GENERATOR

By Adam Maroti
* origin/merge-requests/181:
  Fix kernelimage path quoting

See merge request !181

Closes #153

Compare the symlink target with the destination in `add_file`.
If they match, simply place the file as a regular file in the specified
destination.

Additionally, move the "overwriting/adding file" message right before the
file is added. Showing the message before `add_dir` runs makes the verbose
output confusing, since it says that it adds the directory after the file
it is in.

Fixes https://bugs.archlinux.org/task/76812.
Fixes #154.

Related to #141
Fixes https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/work_items/4235

Account for there being (multiple) spaces in the shebang.

If `type -P` finds the interpreter in PATH on BUILDROOT, then there is no
need to assign the new value and use it for lookup later. At that stage
the interpreter has been found to exist.

The functions are specific to the `sd-vconsole` hook and since there
already is a subshell there, let's place the functions inside it to
prevent them being available in the global scope.

* origin/merge-requests/170:
  Hexdump removal
  Added bats-support for proper error formatting

* origin/merge-requests/174:
  Test coverage with kcov

* origin/merge-requests/176:
  Skip lzop test if binary not installed

Include `bats` in the patterns to match in the shebang.
Process the files assuming newline not NUL terminated lines. Currently it
is only luck that the test files match via this method.

Related to #147

Co-authored-by: Ethan Sommer <e5ten.arch@gmail.com>

Use `cp --remove-destination` in `add_file` to remove the destination
file. Without this, if the destination file is an existing symlink, it
will be the link target that will get overwritten, not the symlink.

* origin/merge-requests/161:
  CHANGELOG: document mkinitcpio v34

Use consistent shebangs:

* `#!/usr/bin/env bash` for bash,
* `#!/usr/bin/ash` for ash,
* `#!/bin/sh` for POSIX sh,
* `#!/usr/bin/env bats` for bats.

Fixes #147

Calling them binaries is not correct. They could be called executables,
but since we do not enforce the execute (`+x`) permissions on the added
files, it would be wrong too.
Since they have shebangs, they are scripts, so let's call them that.