Skip to content

Use Ukify for uki creation if available

cedric cvl requested to merge clavelc/mkinitcpio:ukify_backend into master

Use systemd's native ukify for UKI creation if available.

  • ukify is used by default
  • mkinitcpio's own logic is retained and used if ukify is not available

Ukify is still configurable with a config file (etc/systemd/ukify.conf or equivalent) for everything in UKI Section, via --ukiconfig <path> switch. But mkinitcpio's own parameters will take precedence for --linux, --initrd, --splash, --os-release, and --uname.

I've retained most of the logic and variable names from build_uki for simplicity :)

Edited by cedric cvl

Merge request reports