Calm down... Yes, I'm not one to do much testing of my own testing. Yes,
I'm VERY apt to make stupid mistakes. No, I'm not an idiot. My point is
simple: there is NO need to bring all current [Cc]onfig.in files into strict
complience with spec, only to then rip them all down anyway. We just need
to write our libary to be liberal in what it accepts. Here is MY version of
the plan. If you don't like it, please tell me why. There is no need to
tell me that you will quit if it isn't done your way.
1) Write a generic parsing service for [Cc]onfig.in files, and one frontend
for it (the simple "make config"/"make oldconfig").
2) Test.
3) Write xcnofig.
4) Test.
5) Write menuconfig?
6) Test? (I'm not certian if menuconfig is currently very useful. If you
want a console-based config, run config. If you want menus, use X.)
7) Debate on the new .cfg format.
8) Finalise
9) Add support for it to the backend.
10) Start re-writing the [Cc]onfig.in files into foo.cfg files.
11) Once all of the files are changed, remove support for the old format
from the libary.
12) Fix bugs for the rest of our misirable existances.
-=- James Mastros
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu