"Eric S. Raymond" wrote:
>
> Giacomo Catenazzi <cate@dplanet.
> > Now if I 'make oldconfig' with my old CML1 .config and CML2 oldconfig, I
> > should
> > confirm all 'No' options. (and menuconfig show "NEW" to all 'N' options).
> > I want that your CML2 (probably in makefile) implements something as
> > actual Configure,
> > so that it translates '# CONFIG_FOO is not" to "CONFIG_FOO=no" in the long
> > transition phase. (IMHO people will migrate from CML1 to CML2 nearly the
> > release
> > of 2.5.2 (developers) and 2.6.x (normal/expert people), so this
> > transition phase
> > is very long)
>
> Do you mean that you want me to generate .config-is-not?
no, but that you use also the "#CONFIG_FOO is not" setting.
>
> I could do that easily enough in configtrans.py. But I don't see any
> evidence that anyone has ever actually used .config-is-not for anything.
> If there had been demand for it, the feature would have been ported to
> the menuconfig and xconfig scripts long ago.
>
configtrans.py traslates also CML1 config to CML2 format, right?
Why you don't call configtrans.py (to translate the config) also before
the cmlconfigure.py in the makefile ?
giacomo
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel
