busybox mdev is the fallback dev handler and should always be there.
Ensure that it is, even if other package pulls in other udev handler as
dependency.
This fixes issue where multipath-tools prevent mdev openrc script to get
installed due to dependency of eudev.
Fixes https://gitlab.alpinelinux.org/alpine/aports/-/issues/14877
This reverts commit d1014c82b176 (main/alpine-base: depend on
dev-openrc)
this is useful to not create .apk-new's for something that should never
be edited anyway and always overwritten, but that might be edited by
accident, preventing replacement of a newer release version.
With the various restructuring changes in Alpine Edge around
mdev/mdevd/udev I have found during testing on a system being converted
to eudev/udev use that whenever "setup-devd udev" does a
"apk add eudev udev-init-scripts udev-init-scripts-openrc" this not
only automatically triggers the removal of the busybox-mdev-openrc
package but also the removal of mdev-conf.
mdev-conf contains various mdev configuration related files that are
required on all Alpine systems regardless of which of mdev/mdevd/udev
is in use - if mdev-conf is removed then any time mkinitfs rebuilds the
initramfs file (such as when triggered by a kernel package update) the
resultant initramfs will have NO mdev support and so the machine will
fail to boot.
This change ensures that mdev-conf is always a dependancy.
Since we separated busybox-mdev-openrc from busybox-openrc,
we need to add a dependency to the virtual device manager init
script, so at least one device manager is always installed when
alpine-base is installed.
Also add options="!check" to APKBUILD to avoid the warning.
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Also remove obsolete post-install/post-upgrade script.
People upgrading from busybox-initscripts will have run it;
people directly installing busybox-openrc do not need it
because the base we install already has the necessary modifications.
Signed-off-by: Laurent Bercot <ska@appnovation.com>
At present, the Alpine docker image build process and tools like
apko have to recreate the release data. By providing it as a
distinct package, it is possible to get the authoritative release
data without having to pull in the entirety of alpine-base.
