On Tue, Feb 06, 2007 at 11:04:31AM -0500, Bill Davidsen wrote:I didn't say that clearly, I meant that the information to do this was present, not the functionality.
There's no reason we shouldn't be able to do exactly that with configPerhaps this is because there is a lacking keyword. The depends controls visibility, perhaps a "requires" could be used to provide advisory information which mean "these other things will be turned on if you build this feature."
symbols in Kconfig-land. The only difference is that we've got
slightly different semantics for our "depend" keyword. Things which
don't have their "depend" requirements met aren't offered as options.
Whereas "select" is "automatically pull in dependencies"
apt/yum-style.
"require" is a bad name as it's a synonym of "depend".
While we're at it, it would also be nice to be able to do:I think depends and select provide this now, the postulated "requires" might make building the trees easier.
$ kconfig enable ACPI
CONFIG_ACPI conflicts with CONFIG_APM
$ kconfig enable -F ACPI
disabling CONFIG_APM
$ kconfig disable SCSI
CONFIG_USB_STORAGE depends on CONFIG_SCSI
$ kconfig disable -f SCSI
disabling USB_STORAGE
$ make
The above is all about having a scriptable command line interface so
that people don't need the broken sed + make oldconfig thing.