From: Justin M. Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3870#note_2516172137 I can think of no reason ever really to use make dist-rhel-configs or make dist-fedora-configs unless you are just trying to generate new configs for some reason for a local build. Even then, if you changed configs at all (and why would you run these if not?), you need to validate that the configs are not broken with make dist-configs-check. If you are building anything around the srpm or dist-git, you need the output of make dist-configs-check as make dist-configs creates invalid filenames, and leaves out half of the configs that the spec requires. If you are testing config changes, you must run make dist-configs-check or you risk submitting a broken config. The only time you only need one flavor of configs (fedora or rhel) is once rhel has branched and Makefile.variables has been changed to `INCLUDE_FEDORA_FILES=0` and then make dist-configs-check should also do the right thing. -- _______________________________________________ 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
