On Thu, 30 Oct 2014, Taylor R Campbell wrote:
It seems to me that while depending on ordering for definitions,
files, &c., may be no good, for selections the language of
include "GENERIC"
no options DIAGNOSTIC
no agp*
is still valuable.
I don't mind how it's implemented, but my main concern is that I
want an example like the above to "work". I want it to mean: my
kernel should be based on GENERIC with some changes; whether or
not "options DIAGNOSTIC" is present in GENERIC, my kernel should
not have "options DIAGNOSTIC"; and whether or not anything related
to agp is present in GENERIC, my kernel should not have any agp
devices (and should not have anything that depends on agp). I
do not want error messages like "options DIAGNOSTIC was already
off, so you are not allowed to try to turn it off again" or "there
were no agp devices, so you are not allowed to try to remove agp
devices".
So config(1) ought to choose whatever is the last yes/no answer
for a selection in order to decide what things are really
enabled or disabled, and then process dependencies recursively
from there, rather than incrementally processing dependencies as
the parser makes progress.
That sounds as though it would do what I want.
--apb (Alan Barrett)