From: Jarod Wilson on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3592#note_2296791950 I believe this is actually correct. If the config is explicitly set to off, the build infrastructure should complain if it ends up enabled when the merged config file is generated. The configshook should also highlight any cases where this is going to happen ahead of time, though it won't explicitly sound an alarm itself, but I believe the ensuing artifact build should fail due to the mismatch. At least, I want to say the "with_configchecks" option should cover this?... It does pass the -c option to process_configs.sh, for which the help text says "error on mismatched config options". -- _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
