# Re: \[RFC PATCH\] Kconfig: Enable Kconfig fragments to be used for defconfig

- From: Linus Torvalds \<torvalds@linux-foundation.org\>
- Date: 2010-07-16 18:54:06 
- List: linuxppc-dev
- Page: https://ratatoskr.run/linuxppc-dev/2010/07/3594419
- Thread: https://ratatoskr.run/linuxppc-dev/2010/07/3593087/t.md

```text
On Fri, Jul 16, 2010 at 11:40 AM, Nicolas Pitre [ref] wrote:
>
> DOH.

Well, it's possible that the correct approach is a mixture.

Automatically do the trivial cases (recursive selects, dependencies
that are simple or of the form "x && y" etc), and warn about the cases
that aren't trivial (where "not trivial" may not necessarily be about
fundamentally ambiguous ones, but just "complex enough that I won't
even try").

Maybe a full "solver" is unnecessary, for example, but just a simple
"automatically enable the direct dependencies and scream when it's not
simple any more" would take care of 99% of the common cases, and then
warn when it needs some manual help.

So it's not a strict "one or the other" issue. The solution could be
"some of both".

                     Linus
```
