Linus has let the cat out of the bag that 2.5 "looks like it will open
in a week or two" <http://lwn.net/daily/2.5-coming.php3>. The CML2
and new-makefiles cutover is still, as of Linus's last ukase on the
subject, scheduled for sometime between 2.5.1 and 2.5.2. Linus chose
a sharp cutover; when CML2 and Keith's new makefile system go in, the
old CML1 stuff will drop out.
Given these facts, I think it would be smart for the kbuild team to
develop a transition plan, with milestones. Publishing this as a
request for comments seems likely to smooth our path with Linus and
to reduce grumbling on lkml to a minimum.
In my ideal scenario, we develop a roadmap which is published to
lkml on behalf of the whole build team by somebody who is (a) neither
Keith nor me, and (b) preferably mec in his capacity as
honcho of the build team. Linus and Alan signal agreement, and
everything is on rails except the exact timing.
What will probably happen instead is that Alan will grumble something
not too negative into his beard and Linus will remain gnomicly silent
but merge our patches in his own good time. Still, if the roadmap
keeps other people from bitching by helping them know what to expect
it will be a worthwhile exercise.
So, one big question is, what order are we going to send our patches
in? Do we want CML2 in first, or new makefiles in first? I don't
care, personally, but I'd like to have a path mapped out.
--
<a href="http://www.tuxedo.org/~esr/";>Eric S. Raymond</a>
The kind of charity you can force out of people nourishes about as much as
the kind of love you can buy --- and spreads even nastier diseases.
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel
