Kernel scriptlets have these parameters: name, version, release, kernelrelease, flavor, variant, usrmerged, image, certs Eliminated parameters: suffix (removed, only used for vanilla kernel) systemmap (inferred from usrmerged) modules_dir (inferred from usrmerged) The parameters inferred from usrmerged are baked into a number of scripts throughout the distribution so these can be baked in here as well. variant is currently not used in the binary scripts but cannot be inferred - this can be used to tie the binary package to a source package usrmerged is necessary because non-usrmerged kernels should be installable on usrmerged distributions (with usrmerged s-m-t) that have compatibility symlinks (currently all) kernelrelease is non-trivial to infer and the way it is inferred has been updated a number of times recently flavor could be inferred for the base package but not for subpackages like kernel-default-base that share the same script image is hard to infer and needs updating for new architectures certs depends on project configuration name. version, and release was baked into the script by the templating mechanisms and the script was tehn reused by kernel-default-base - this should continue working unchanged For certificate scripts there are two parameters: certs, kmp The code for kmp parameter is # Only apply CA check on the kernel package certs (bsc#1173115) if [ -z "$kmp" ] && mokutil -h | grep -q "ca-check"; then MOK_ARG="--ca-check" Maybe there is a more descriptiev name that could be used? The parameters for KMP scripts are: name, version, release, kernelrelease, flavor, usrmerged These are the only parameters available at KMP build time.