On Fri, 2016-08-26 at 09:37 -0700, Laura Abbott wrote:
I think this is where we are disagreeing. For an experienced
individual,
accepting all configurations is the right thing to do. Mismatched
configurations have a much bigger impact for maintainers though
because a mismatched configuration is going to go out to many more users.
It's hard for me to evaluate this since I still do not know what
"mismatched configurations" actually are.
It's much easier just to reject bad configurations. The same is
true
for newer users, if there's no error, it's much harder to go back and
debug a configuration issue versus just rejecting it outright.
Let's take listnewconfig.
I _think_ I understand why the people taking care of kernel.spec like
to see (what might or might not be relevant in) its output. But for
people buidling locally it's much less interesting. (I've been happy to
ignore it for years. I just rebase on Fedora's latest and greatest
.config every now and then and be done with it.)
To put it another way: it seems this is something that is fatal by
default and is mostly relevant for those maintaining kernel.spec but
less relevant for people building kernel rpms locally. Building the
kernel rpms locally is hard enough already. Do we need to make it a bit
harder by default?
Paul Bolle