Background to the argument about CML2 design philosophy
Quoted 7 lines · On 05/21/2001 at 05:04:40 AM [email protected] wrote:
See, I've already written off the chronic bellyachers. Since I can't please them without scrapping the whole plan, I'm going to ignore them. In particular, anybody who repeated "fsck Python..." after Linus ruled that Python is not an issue and Greg Banks announced the C implementation of CML2 has got a sufficiently severe case of rectocranial insertion that they've defined themselves out of the conversation.
I probably qualify as one of the bellyachers. If so, I apologize. It was not my intention to disparage the work of Eric or anyone else involved in this project.
Speaking from the perspective of a user of the CML tools, rather than as a developer, all I've been trying to say is this: When I type "make menuconfig" or "make oldconfig" in the future, I want to see the same interface and the same results that I've always seen, because it's always worked for me in the past. It really doesn't matter to me if, down underneath, this is being done by CML1, CML2, or a little man in my computer who slaughters chickens and reads their entrails for omens to determine dependencies. Right now I can grab a new -pre or -ac patch, use oldconfig, and have a compile going in a few minutes, without knowing or caring about the details of the config process. In the rare case that a patch breaks an existing driver, it takes only a couple of minutes with menuconfig to disable that driver and compile without it, and then put it back in when it's fixed. And when, every once in a great while, I decide to scrap my .config and start over, I can fly through all the menuconfig options very quickly and make my customary selections almost without thinking about it.
I just want to be able to keep using the tools in this way. If that's not going to be possible... well, I'll adapt. But from my point of view, learning a new set of tools just to keep doing the same things I've always done isn't a pleasant prospect. I understand that changes may be necessary to meet others' needs, but I'd like to see those changes made without affecting the way my own needs are met.
I'm off my soapbox now and won't bellyache about it any further.
Wayne
[email protected] <[email protected]>:
Quoted 5 lines
Speaking from the perspective of a user of the CML tools, rather than as a developer, all I've been trying to say is this: When I type "make menuconfig" or "make oldconfig" in the future, I want to see the same interface and the same results that I've always seen, because it's always worked for me in the past.
Visual details will differ, but I've been careful about maintaining functional compatibility. There was a phase of the development during which I was mostly processing feature requests from people who wanted features of the old system that I had not properly understood (such as the NEW tag). That phase ended almost a month ago. Nobody who has actually tried the CML2 tools more recently has reported that the UI changes present any difficulty.
CML2 drops its configuration results in the same place, in the same formats, as CML1. So you should in fact be able to type make menuconfig' and make oldconfig' with good results. Have you actually tried this?
Signature · 8 lines
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
The right of the citizens to keep and bear arms has justly been considered as
the palladium of the liberties of a republic; since it offers a strong moral
check against usurpation and arbitrary power of rulers; and will generally,
even if these are successful in the first instance, enable the people to resist
and triumph over them."
-- Supreme Court Justice Joseph Story of the John Marshall CourtQuoted 3 lines · Eric S. Raymond
the NEW tag). That phase ended almost a month ago. Nobody who has actually tried the CML2 tools more recently has reported that the UI changes present any difficulty.
What happened with the discussion on configurable colors in make menuconfig? Darkblue on black as frozen options get isn't exactly optimal ... at least not for my eyes. Being next to a bold, white text doesn't help either.
Quoted 3 lines
CML2 drops its configuration results in the same place, in the same formats, as CML1. So you should in fact be able to type
make menuconfig' andmake oldconfig' with good results. Have you actually tried this?
It works for me, but anyone testing this should know that the CML2 tools read "config.out" if it finds one. So people that do things like:
make mrproper ; cp ../.config-2.4 .config ; make oldconfig
will have to change to copying config.out instead. Doing like this sort of works* if there is no config.out, otherwise it does not (as it uses the config.out).
Saying that the config result ends up in the same place and same format is somewhat misleading, you do get a copy in the CML1 output format but the tools doesn't care about that if it can find a file in the new format.
*) "Sort of works", since doing like I do will cause you to get a lot of questions that you have already answered. That appears to be a one-time problem as 'oldconfig' does not read "# CONFIG_FOO is not set" as "no". Would be nice if it did.
make mrproper doesn't remove config.out. It should since that's what it does with .config* files. Not sure if it should remove the rules.out file also, but I think it should as the idea(?) with mrproper is to clean up anything that is generated.
/Urban
Urban Widmark <[email protected]>:
Quoted 4 lines
What happened with the discussion on configurable colors in make menuconfig? Darkblue on black as frozen options get isn't exactly optimal ... at least not for my eyes. Being next to a bold, white text doesn't help either.
Nobody could come up with a way to support configurable colors that didn't seem like way more trouble than it was worth.
Signature · 5 lines
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
"...quemadmodum gladius neminem occidit, occidentis telum est."
[...a sword never kills anybody; it's a tool in the killer's hand.]
-- (Lucius Annaeus) Seneca "the Younger" (ca. 4 BC-65 AD),Quoted 10 lines · Urban Widmark
Quoted 3 lines · Eric S. Raymond
the NEW tag). That phase ended almost a month ago. Nobody who has actually tried the CML2 tools more recently has reported that the UI changes present any difficulty.
What happened with the discussion on configurable colors in make menuconfig? Darkblue on black as frozen options get isn't exactly optimal ... at least not for my eyes. Being next to a bold, white text doesn't help either.
if you don't like dark blue on black, change your terminal colours. then you won't find it hard to read in other applications either.
it's also far less effort this way...
j.
Signature · 1 line
"Bobby, jiggle Grandpa's rat so it looks alive, please" -- gary larson
Quoted 6 lines · john slee
Quoted 5 lines · Urban Widmark
Quoted 3 lines · Eric S. Raymond
the NEW tag). That phase ended almost a month ago. Nobody who has actually tried the CML2 tools more recently has reported that the UI changes present any difficulty.
Quoted 7 lines
Quoted 4 lines
What happened with the discussion on configurable colors in make menuconfig? Darkblue on black as frozen options get isn't exactly optimal ... at least not for my eyes. Being next to a bold, white text doesn't help either.
if you don't like dark blue on black, change your terminal colours. then you won't find it hard to read in other applications either.
On the first day of my graduate course 'Advanced Topics in Computer Graphics' the professor walked in and wrote on the blackboard "Never Use Blue on Black".
Yes, we had blackboards then. No, our eyes have not evolved since then. ;-)
--
Daniel