Hmm... I though, at it's root, the configuration language is defined as an
interpertive language. The way I think menuconfig should be handling this
is such:
1) Process the defconfig, setting the values as defined there ("# foo is not
set" <=> foo='n'
2) Process the .config (if it exists), setting the values as definded there.
loop {
3) Build the menus from the [Cc]onfig.in (as a preformance hack, possibly
build a database of linkages, and don't re-parse the [Cc]onfig.ins each
time).
4) Get user input.
} while (!exited);
Bampf. No more problems with variables equal to "" (assuming the defconfigs
have been updated. Otherwise, the results will be the same as the other
configs.
-=- James Mastros
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu