kirk> if [ "$CONFIG_PARPORT" = "y" -o "$CONFIG_PARPORT" = "n" ] ; then
kirk> define_bool CONFIG_PARIDE_PARPORT y
kirk> else
kirk> define_bool CONFIG_PARIDE_PARPORT m
kirk> fi
grant> PARIDE can be built with or without PARPORT support. However, if PARPORT
grant> is configured but not present in the kernel, PARIDE must also be built
grant> as a loadable module.
So, specifically, that "$CONFIG_PARPORT" = "n" is correct?
> Perhaps there is a better idiom for doing this, but I don't know what it
> is.
I've spent hours and hours poring over Config.in files. I think this
idiom is fine, if that is what the semantics really are. It will work
with config/oldconfig/menuconfig/xconfig. But it merits some commenting.
I thought it was a bug, too.
Michael Chastain
<mailto:mec@shout.net>
"love without fear"