Re: [2.6 patch] select FW_LOADER -> depends HOTPLUG

[Roman Zippel]

On Tue, 10 Aug 2004, Sam Ravnborg wrote:

> On Tue, Aug 10, 2004 at 10:44:11AM +0200, Adrian Bunk wrote:
> > 
> > I assume Sam thinks in the direction to let a symbol inherit the 
> > dependencies off all symbols it selects.
> > 
> > E.g. in
> > 
> > config A
> > 	depends on B
> > 
> > config C
> > 	select A
>         depends on Z
> 
>   config Z
>         depends on Y
> > 
> > 
> > C should be treated as if it would depend on B.

There are two problems:
1) If A has no prompt it's not visible and so it's dependency is 'n', this 
means a number of symbols wouldn't be visible anymore.
2) It would change the bahaviour of symbols, which already do multiple 
selects (e.g. CONFIG_INET_AH), the select of CRYPTO would be useless, as 
it would only become visible, when CRYPTO is enabled. This means such 
selects wouldn't be possible anymore.

This really needs a different (but similiar) mechanism, what I have in 
mind is something like this:

config A
	autoselect

config B
	depends on A

For the visibility calculation A is set to y and A is automatically 
selected if any symbol, which depends on A, is enabled.

> Correct. But at the same time I miss some functionality to
> tell me what a given symbol:
> 1) depends on
> 2) selects
> 
> It would be nice in menuconfig to see what config symbol
> that has dependencies and/or side effects. 

xconfig has something like this, if you enable 'Debug Info', although it 
rather dumps the internal representation.
Adding something like this to menuconfig, would mean hacking lxdialog, 
which is rather at the bottom of the list of things I want to do. :)

bye, Roman
-
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/