The mconfig release 0.20 is now available.
Mconfig is a tool to configure the linux kernel, similar to
make {menu,x,}config, but written in C and with a proper yacc
parser.
The following changes have been made since the last public
release, 0.18 by Michael Elizabeth Chastain:
* switched to autoconf/automake.
* build 'menu' mode only if curses are available.
* added manpage (VERY simple).
* added specfile for RPM builds.
* help text moved from C source to external file.
* modes 'text' and 'old' implemented.
* verb 'dep_mbool' implemented.
* relaxed error checking - moan in
This release is available as gzip/bzip compressed source tarball at:
ftp://ftp.kernel.org/pub/linux/kernel/people/hch/mconfig/
ftp:/ftp.opengfs.org/pub/opengfs/0.0.91/opengfs-0.0.91.tar.gz
ftp:/ftp.opengfs.org/pub/opengfs/0.0.91/opengfs-0.0.91-1.src.rpm
Please send patches and report bugs to me,
Christoph
On Fri, 16 Nov 2001 17:38:40 +0100,
Christoph Hellwig <[email protected]> wrote:
>The mconfig release 0.20 is now available.
>
>Mconfig is a tool to configure the linux kernel, similar to
>make {menu,x,}config, but written in C and with a proper yacc
>parser.
Christoph, could you explain why this is being added now and how it
compares to CML1 and/or CML2?
kbuild 2.[45] is completely agnostic about how .config and autoconf.h
are built, the only requirement is that .config be internally
consistent before it goes into the main build phase. I don't care how
.config is built, but I do want to understand why another version of
CML is being developed.
On Sat, Nov 17, 2001 at 09:56:51PM +1100, Keith Owens wrote:
> On Fri, 16 Nov 2001 17:38:40 +0100,
> Christoph Hellwig <[email protected]> wrote:
> >The mconfig release 0.20 is now available.
> >
> >Mconfig is a tool to configure the linux kernel, similar to
> >make {menu,x,}config, but written in C and with a proper yacc
> >parser.
>
> Christoph, could you explain why this is being added now and how it
> compares to CML1 and/or CML2?
It's not added now - Michael started the development about 5 years ago,
in 1998 he stopped working on it. In 1999 or 2001 I started hacking on
it, only adding what I needed. Now I finally found the time to make a
formal release.
The tool mconfig parses CML1 rules, and does so _much_ more strictly
then any other parser.
> kbuild 2.[45] is completely agnostic about how .config and autoconf.h
> are built, the only requirement is that .config be internally
> consistent before it goes into the main build phase. I don't care how
> .config is built, but I do want to understand why another version of
> CML is being developed.
The current cml1 scripts are _very_ ugly, and even if cml2 makes it in
2.5 (yes, I don't like it - but I don't have to decide it..) kernels
using cml1 will be around for a long time.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
Personally i tried mconfig just now, and i was charmed by its speed,
comparing to the one of the current cml1 implementation...
Yes that was poor old p166...
I think i`ll stick to it for a while now...
cheers, Samium Gromoff...