On Fri, Feb 15, 2002 at 09:33:01AM -0700, Steven Cole wrote: > On Friday 15 February 2002 09:04, Tom Rini wrote: > > On Fri, Feb 15, 2002 at 11:22:00AM +0100, Giacomo Catenazzi wrote: > [much sippage] > > > 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. > > Agreed, but it is a minor irritation for me, and could be a major irritation > for others. On my RH 7.2 system, the lpd startup scripts don't work with > anything but Python 1.5.2, so I have to switch things around a little if I > want to get lpd working. This is very easy to do, and I don't have this > problem on Mandrake which is fully compatible with Python 2.
It's possible to have python 2.x be 'python2'. > > 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. > > This is an extremely important point. When applications > such as make xconfig and make menuconfig have been around > a long time, a set of users will exist who will STRONGLY > resist any change to the look and feel and operation of > the interfaces to those programs. It's not so much the look & feel (which seems to have been copied well by now), but policy changes. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
