The kernel xz implementation can only handle crc32 or none integrity
check but the xz default is crc64 and the kernel will panic.

xz is faster (in particular because it uses multiple cpu cores)
and the resulting initrd has the same size (up to 0.5MB)

findmnt always returns the absolute path to a mount point, so
we have to compare the result with an absolute path.
But $(IMAGE_DIR) may be a relative path; thus, convert it to an
absolute path first.

This fixes the "No space left on device" error that occured when
updating large files (e.g. a squashfs) on the image partition file.

The offical singular-version is either uses old packages
or installs automatically package sources. The Debian-Version
seems to be reasonable sane.

This allows us to execute the early config in normal mode and thus,
we can use things like "if" etc.

may have to unmount the partition image to operate cleanly.

This allows make to track the target as dependency. In particular,
it can now be triggered by the target image_content. Hence, it is
no longer neccessary to call it manually

as "fronted" for image_assemble.

Some targets require the image partition to be mounted.
Although, it is easy to detect this (and mount the partition)
by depending on the phony target image_mount_if, make is unable
to calculate the dependencies correctly. The reason is that some
dependencies are located on the partition (which is not mounted
when scanning for dependencies). Hence, make will rebuild all
targets (after it mounted the partition) regardless of the state
of these files.

To solve this issue we introduce ensure_mount and call it on phony
targets invoked by the user. The actual target will be converted and
serve as wrapper which mounts the partition and then invokes the actual
target renamed to <name>__ignore_mount.

Nowadays, lipck generates its own image with up to date bootloaders,
etc. Furthermore, a brand new sparse multiboot image may be created
using the multiboot target of lipck. So the blob is no longer
useful in any way.

This target may be used to create an empty multiboot image (only the
bootloader is installed). This is intended to be used manually to
either debug the crucial part of the bootloader installation, or just
because a multiboot image comes in handy for another purpose.

Previously, the efi bootloaders were installed in several places.
The main reason was to be compatible with the lipstick grub.cfg
and the ubuntu secure boot grub. This commit unifies the location.
Hence, old lipstick grub.cfg`s are no longer compatible; we need at
least commit
	786f37351916396cb59d21e573d6be372089e516
of the lipstick repository to have a (fully) working grub.cfg.

(i.e. at the same time the content is created)