I have some comment/explications about the thread
The discussion was also on lkml, ESR asked to kbuild
people to give some comments, using also the feed-back
As you noticed, in lkml the discussion went into flames,
fogetting the important points.
[As this flame is going forgetting kbuild-2.5..]]
The comments in kbuild list are accessible to all.
You should read them (hmm, really there are only one full
comment [my comment] + discution/flame]
The importants points are:
CML2 and kbuild-2.5 are two different projects, which
don't depend each other.
The need of the two project is also demostrated by the
other never finished similar project (mconfig, kernconfig,
mcml2, cml2config, dancing-makefiles, ...)
Nobody talked about kbuild-2.5. It really correct actual
makefiles. And I hope that Linus correct this bahaviour in
a time manner (and not as last big makefile correction in
What wrong with kbuild-2.5?
Keith seems to comunicate better with other kernel developers,
[The main point of kbuild-2.5 are:
no more required make mrproper -> faster,
no more 'touch include/*/*.h',
multiple trees, read-oly sources,...]
Old configuration programs, IMHO, are not so broken, but there
is a big problem of maintainability. Every 10 patches, few are
Few developers (maybe no developers) will use xconfig, and
also few developers have read the Documentation/kbuild/.
This inevitably port people to write Config.in as bash
shell (WRONG!), forgetting that unset configuration have
variable unset OR set to 'n'.
These problems seems not so huge, but with actual kernel
development there are. It is difficult to push corection patch
into the main kernel. Who will help kbuild people?
[CML2 will solve the problem at the source: same engine for
all interface, with more checks, so original sender will have
the correct config.in].
Andrea'WAlan did you make some tools for CML1 and did you not
publish? Why? (not published == not existance from the other
Read who wrote menuconfig, and you see why ESR want to
Read some user list about configuration problem and you see
that CML1 cause user much problem that a kernel hacker see.
(menuconfig didn't compile, where is such symbols?)
No flame please.
Tell us what is wrong in kbuild-2-5 and in CML2. Don't flame!
If you flame about CML2, ESR will answer you and then he
forget the initial proposal of improvement.
giacomo, who don't understan why kbuild-2.5 is not in kernel
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/