Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]

[Sam Ravnborg]

On Fri, Sep 01, 2006 at 07:51:39PM +0200, Stefan Richter wrote:
> 
> It will get difficult to entirely please users who don't use these 
> interfaces to .config.

We have a number of more or less friendly interfaces to configure
the kernel. Yet some people prefer to directly modify the .config.
That is fine let them do so.
But to get an overview over the sometimes complex logic thay have
to turn to move powerfull tools such as menuconfig.

Editing .config is a second class citizen way of configuring the
kernel, and menuconfig is first class IMHO.

So enhancing the .config file to express the dependencies
is not the way forward. We should do this in menuconfig (and friends)
and let users use the dedicated interface to edit their kernel
configuration using the dedicated tools and not by editing .config.

Much of the discussion are centered about "select" which is indeed
ugly are in some cases ill-used.
But prime issue is that using select makes it hard to
un-select certain configuration items. And avoiding select makes it
un-intuitive to enable some configuration items.
So we simple needs to:
1) Make is easy to un-select selected configuration items by unselecting
   the relevant items
2) Make it possible to select 'non-visible' options by providing a way
   to satisfy the dependencies.

And maybe 2) makes select almost obsolete..

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