Dave Jones wrote:
> Having it documented obviously isn't enough too.
Maybe we need some heuristics for "upgrading" old .config files in
the event of a "make oldconfig". They could be of the form of rules
like this:
CONFIG_obsolete1 && CONFIG_obsolete2 -> CONFIG_new1=y, CONFIG_new2=y
(In a separate file, and entries would be aged. Maybe config tools
could even walk users through this interactively, or flag settings
obtained this way specially, e.g. with a similing wizard icon ;-)
Maybe even add some descriptive text after the rule.)
This still doesn't help for hard to find or obscurely named options,
but at least people upgrading wouldn't be bitten every time something
is renamed or restructured.
- Werner
-- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net / /_http://www.almesberger.net/____________________________________________/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Nov 07 2002 - 22:00:31 EST