On Thu, 23 Aug 2001, Daniel Phillips did have cause to say:
> Take a close look at the word "just" in that sentence. Kernel configuration
> is not a trivial task at all and it gets less trivial every time Linux gets
> more general.
I don't disagree. But the point isn't how trivial or non-trivial the task
of configuring the kernel is, the point is for a lot of people it is the
ONLY task that they will use python for. And everyone who builds a kernel
will have gcc, so thats the 'ideal' dependency. Second and third most
likely, a C++ compiler or perl (depending on what you figure the
installbase of each one is). Forth, some form of java runtime. And after
that is python. (I'm not advocating using any of the above for kernel
configuration. But they are more likely to already be installed than
python is.)
What this says is that either linux sources are going to grow (and the
build process get more complex) by whatever the size of the python
interpreter is, OR some method will be used that doesn't require a
separate interpreter.
This is also in agreement with his statement about reducing the dependence
on external tools, whereas requiring everyone to install python does not.
It could either be read as using straight gcc C -or- as including all the
external tools in buildable form. I'm betting on the former.
--- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 [www.ebb.org/ungeek] GIT/CC/CM/AT d--(-)@ s+:-- a-->? C++++$ ULBS*++++$ P- L+++>+++++ E--- W+++ N+@ o+>$ K? w--->+++++ O- M V-- PS+() PE Y+@ PGP++() t 5--- X-- R tv+@ b++++>$ DI++++ D++(+++) G++ e* h(-)* r++ y++ ------END GEEK CODE BLOCK------ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:01:00 EST