Re: [kconfig] Survival of scripts/Menuconfig?

[Petr Baudis <pasky@ucw.cz>]

Dear diary, on Sun, Nov 03, 2002 at 06:56:53PM CET, I got a letter,
where Roman Zippel <zippel@linux-m68k.org> told me, that...
> On Sun, 3 Nov 2002, Petr Baudis wrote:
> >   I'm asking because I want to move the relevant lxdialog functionality to
> > scripts/kconfig/mconf.c (I think it makes no sense to call lxdialog externally
> > from mconf.c) and get rid of the separate lxdialog tree. And scripts/Menuconfig
> > is the only other user of lxdialog.
> 
> What do you plan to do with it exactly?

After looking at it further, it turned out that the lxdialog code I want to
preserve is larger than expected, thus I will make it a library rather than
pumping all the stuff to mconf.c. Still huge advantage against having to call
the external binary everytime (also, we won't have that ugly flickering anymore
;-).

> In any case could you start with a copy of mconf.c? We are past feature 
> freeze now, so it makes little sense to remove lxdialog, but it could be 
> distributed separately together with the qt/gtk version.

Well, I think that it's not so good idea to have menuconfig distributed
separately, since it is probably the best thing you can get out of the text
mode, and there're really not much alternatives you could dream out. Having the
make config as the only way to configure the kernel is not a good thing, IMHO.

Also, as I said above, I decided to rather transform lxdialog to a library,
which is not so big change, IMHO.

-- 
 
				Petr "Pasky" Baudis
.
This host is a black hole at HTTP wavelengths. GETs go in, and nothing
comes out, not even Hawking radiation.
                -- Graaagh the Mighty on rec.games.roguelike.angband
.
Public PGP key && geekcode && homepage: http://pasky.ji.cz/~pasky/