Re: [kbuild-devel] Converting the 2.5 kernel to kbuild 2.5

Tom Rini (trini@kernel.crashing.org)
Tue, 4 Dec 2001 11:13:37 -0700


On Tue, Dec 04, 2001 at 06:27:26PM +0100, Martin Dalecki wrote:
> Alan Cox wrote:
> >
> > > Creating a dependency on Python? Is a non-issue. Current systems that
> > > are to run 2.5 or 2.6 are bloated beyond belief by glibc already, Python
> > > is nice and it does not create such unmaintainable mess. Whether
> >
> > Python2 - which means most users dont have it.

Most users sure as hell shouldn't be playing with 2.5.x right now
anyways. With any sort of 'luck' it'll be 6 months at least before
2.5.x becomes stable enough that it will probably compile all the time
again and not have a random fs eating bug. In 6 months even woody might
be frozen :)

> And then you will end with:
>
> python1.4x,
> python2,
> python3 rewrite in python1 and so on and so on.

Say what? Python (with the exception of undocumented features) has been
pretty good about compatiblity. If it works with 1.5.x and doesn't rely
on undocumented features, it'll work with 2.0x, 2.1x and 2.2x.

> Thanks but NO thanks

Then go help Greg Banks in his CML2-in-C project.

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
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/