Re: RFC: kconfig select warnings bogus?

Stefan Richter
2007-05-20T11:46:18Z

Trent Piepho wrote:
> On Sun, 20 May 2007, Stefan Richter wrote:
>> Basically you replace
>>
>> A... depends on B
>>
>> by
>>
>> B... serves A
>>
>> The latter variant is a pain to maintain. Dependencies change over
>> time, therefore we should note the dependency always at the dependent
>> option, not at the serving option.
>
> The problem is that "B" will not exist on some architectures. If you put the
> dependency with "A", the dependency still exists when "B" is gone. If the
> dependency is with "B", it nicely goes away when "B" is gone.

If "make whateverconfig" works correctly,...

>> Iterating upwards and downwards the dependency graph is the duty of
>> "make snafuconfig", not of the maintainers.

...multi-level dependencies are no problem for it.

There is nothing wrong with

A... depends on B

B... depends on C

# CONFIG_C is not set

-> A is unavailable.
--
Stefan Richter
-=====-=-=== -=-= =-=--