Re: CML2 1.0.0 doesn't remember configuration changes

[esr@thyrsus.com]

jeff millar <jeff@wa1hco.mv.com>:
> From what's in the various documentation and reading about 1% of the cml2
> traffic...  cml2's  various "make *config" invocations use config.out as a
> database for remembering configuration, and then on exit they all generate a
> fresh copy of .config.

Actually CML2's behavior is a bit more orthogonal than that.  It normally
reads nothing and writes to config.out.  You can give it -i and -I options
telling it to read in files at startup, or a -o option to issue output to
a different filename. 

Now here's where it gets a little tricky.  The config.out format is different
from a CML1 .config in that it sores FOO=n settings explicitly, rather than in
the form of "# FOO is not set" comments.  The reason for this is so we can pass
around partial configurations (a particular set of APM options, say) with 
explicit no values in them.  

Eventually (like, when Keith's Makefile stuff goes in) the CML1
.config format will go away.  In the meantime, after each configurator
run, a shim script called "configtrans.py" takes the config.out and
generates both .config and include/kernel/autoconf.h from it.

>     Apparently it's too hard to read the existing
> .config to generate an initial config.out, 

Actually it's easy.  I can feed .configs to cmlconfigure with a -i option and
they'll be read in just fine.  

>                                      so I think "make *config" the
> first time, starts with some default and then on exit _should_ write that to
> config.out.  Then any other invocationn of *make *config". needs to use
> config.out.  "make xconfig", "make config" and "make editconfig" need to
> operate the same way.  I've never use anything but "make xconfig",  "make
> menuconfig" and "make oldconfig" and they currently all operate on the same
> information.  I've never used editconfig and don't know what it's for.

Editconfig was a mistake.  OK, I think I understand the rules now.  Is it:

(1) First, try to read from .config
(2) If .config doesn't exist, read from $(ARCH)/defconfig

?

> 1.0.3 feels faster, btw.

That's because it is.  I am continuing to tune.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

You need only reflect that one of the best ways to get yourself 
a reputation as a dangerous citizen these days is to go about 
repeating the very phrases which our founding fathers used in the 
great struggle for independence.
	-- Attributed to Charles Austin Beard (1874-1948)