Linus Torvalds writes:

quoted text
> Well, that part isn't the one that I think is bothersome - I just wonder 
> if the whole "defconfig" mess is worth keeping with the kernel at _all_.
> 
> It also causes tons of noise whenever I happen to do something like "git 
> grep CONFIG_XYZZY" to see where some config variable is used etc.
> 
> So I was more wondering whether maybe there could be better ways of doing 
> that whole thing. 

Having the defconfigs seems to be useful for the embedded folks,
judging by the number of defconfigs they have.  They generally have a
defconfig for each reference board.

Those defconfigs would be much smaller and change much less often if
they could be expressed as a delta from some other defconfig.  So we'd
end up with a small number of base defconfigs plus a set of board
defconfigs that would say effectively "use the options from that other
defconfig, plus turn this on and that off".

On the whole, I think defconfigs are useful because we have so many
configuration options, and the defaults and help texts for many of the
options are not always helpful.

We could possibly do without defconfigs if we put effort into making
sure that all the "depends" and "default" values in all the Kconfig
files are sensible.  Ideally, a user could select something like
"32-bit powermac support" and take the defaults for everything else,
and get something sensible for a 32-bit powermac.  We're not at that
point, and I think it would take considerable effort to get there.

I would like to see something better than what we have at the moment
(whether one of the two ideas above, or something else) because I find
maintaining the defconfigs a bit of a pain myself.

Paul.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/