Skip to contentSkip to conversation

CML2 design philosophy heads-up

DISCUSSION Pete Zaitcev 1 participant 1 message May 18, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 7 lines
Quoted 4 lines

As for the language CML2 is written in, surely C would work just as well as Python if the config-ruleset file is in a known format. GCC is required for the kernel to build, I don't see why anything else should be required simply to configure it.

Menuconfig is fairly popular, and requires curses.. etc. etc. There isn't a configurator which doesn't require something more than gcc is there?

I always do "vi .config", then "make oldconfig", because it is very convinient, simple, and flexible way to do it. For instance, it is very easy to store a pile of configs for different kernels, very easy do diff them (with -u and without).

I do not have Python installed on any of my machines.

The right way to handle the CML2 problem, IMHO, is to have a C implementation of Python part without curses, tcl, and other crap. Half of ESR's justification is "dynatic loading of components and recovery from failure to load them", which goes away if we do not support extras like curses. Another half was GC, which is just a convinience for a project of CML's size.

-- Pete