[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D33965A.1090505@oracle.com>
Date: Sun, 16 Jan 2011 17:07:38 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Stefan Richter <stefanr@...6.in-berlin.de>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>,
"Nicholas A. Bellinger" <nab@...ux-iscsi.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Joel Becker <jlbec@...lplan.org>,
James Bottomley <James.Bottomley@...e.de>
Subject: Re: [PATCH] configfs: change depends -> select SYSFS
On 01/16/11 16:52, Stefan Richter wrote:
> On Jan 16 Linus Torvalds wrote:
>> Or do you expect a high-quality implementation of a configuration
>> script to allow the user to just say "I want ocfs2", and then figure
>> out the dependencies and solve them for you?
>>
>> I'd say that the latter case is OBVIOUSLY the quality implementation,
>> while the former one is just stupid.
>
> As Al noted, there also needs to be a convenient way to *disable* options.
>
> Hence, the Kconfig files should merely declare the dependencies. Then,
> some user interfaces should deal with the this database of dependencies
> and let different people achieve different goals as easily as possible.
>
> We already have different UIs. But perhaps we have too much UI down in
> the Kconfig files. I.e., perhaps Kconfig shouldn't know the difference
> between depends-on and select. Let the different UIs present the
> dependency graph to the operator in different ways, suitable to different
> tasks.
I agree, I think that the UIs should list a kconfig symbol and its dependencies,
then let the user enable them as needed.
> /handwave off.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists