Re: [Qemu-devel] QEMU and Kconfig

From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Samuel Ortiz" <sameo@linux.intel.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU and Kconfig
Date: Thu, 08 Nov 2018 13:46:39 +0100	[thread overview]
Message-ID: <87va57n3dc.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <9832950d-52e7-da47-d466-98746d3f7a83@redhat.com> (Paolo Bonzini's message of "Thu, 8 Nov 2018 10:56:09 +0100")

Paolo Bonzini <pbonzini@redhat.com> writes:

> On 08/11/2018 09:46, Philippe Mathieu-Daudé wrote:
>> 
>>     Almost; if there's a conflict between the decision from "depends on" and
>>     "select" says, it's an error.  (Likewise if there's a conflict between
>>     default-configs/ on one side, and "depends on"/"select" on the other).
>> 
>>     This is different between kernel Kconfig and minikconf in my git repo.
>>     The difference is because the Kconfig documentation warns against the
>>     surprising effects of "select" blindly enabling the target symbol;
>>     making minikconf stricter avoids those surprises.
>> 
>> 
>> So can we rename your tool Qconfig?
>
> Haha, that's up to whoever finishes the work. :)

There's your chance to leave your mark on QEMU!  SamConfig has a nice
ring to it, doesn't it?  ;-P