On Fri, Feb 15, 2002 at 11:22:00AM +0100, Giacomo Catenazzi wrote: > Eric S. Raymond wrote: > > >kbuild team members: Dirk Hohndel has volunteered to have a chat with > >Linus about the CML2/kbuild-2.5 transition (and, implicitly, the status > >and role of the kbuild team). > > > >Please inform him of: > > > >1) your technical judgement and opinions about CML2 and kbuild-2.5 > > > >2) the problems with the present build system, > > > >3) whether or not you think CML2 and kbuild-2.5 should be mainstreamed > > into the kernel, > > > >4) known remaining problems with CML2 and kbuild-2.5, and what the plans > > are to address them. > > > >He needs to hear from the whole kbuild team and properly understand > >the background of our present rather frustrating situation. [snip] > CML2: [snip] > The big problem in CML2 is python (and python2).
This is a red herring. People bitch and moan about it, but it's not a problem. The real problem with CML2 is 'enhancements' that come with the package. The first round of CML2 that goes into the kernel needs to match the current set, bug/feature for bug/feature, and counter intuitive to normal user question for coutner intuituve to normal user question. Right now symbols without a help entry still won't show up unless CONFIG_ADVANCED is set (right?). And as a case in point (which I told Eric not to do), CONFIG_PPC_RTC is currently a derived symbol instead of being a question (and if I read the derivation right, it's wrong to boot). -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
