KBuild 2.5 Migration

Daniel Phillips (phillips@bonn-fries.net)
Fri, 31 May 2002 06:46:02 +0200


On Friday 31 May 2002 06:01, Skip Ford wrote:
> Thunder from the hill wrote:
> > On Thu, 30 May 2002, Skip Ford wrote:
> > > I could be wrong but I think Linus wants small patches that slowly
> > > convert kbuild24 to kbuild25, and not just a chopped up wholesale
> > > kbuild25.
> >
> > That's what we have. If you want to try kbuild-2.5, you have to use the
> > Makefile-2.5 explicitly. If you don't explicitly do that, you're using
> > kbuild-2.4, so you got a pretty good chance to evaluate kbuild-2.5 and
> > then decide whether you leave it or pull it. Enough migration?
>
> That's not a migration at all. That's two different build systems side
> by side.
>
> A migration would mean that there is only ever 1 build system. Send
> patches that would convert what we have now to kbuild25 over the next 10
> kernel releases or so. That's a migration.

You're 'improving' the meaning of the term a little. Suppose you're
going to migrate all the servers in a company from Windows to Linux, do
you come up with a succesion of intermediate operating systems? IOW, in
a migration, it is the users who migrate, not the software. I believe
the term you were thinking of is 'evolution'.

-- 
Daniel
-
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/