Re: [BK PATCH] klibc for 2.5.64 - try 2

Roman Zippel (zippel@linux-m68k.org)
Sat, 8 Mar 2003 03:26:24 +0100 (CET)


Hi,

On Fri, 7 Mar 2003, David Lang wrote:

> > There is still the possibility to support multiple libc implementation, if
> > you don't like dietlibc, you're still free to use klibc.
>
> along the same lines if you don't like klibc you are free to use or
> implement dietlibc or anything else.

Using it and including it into the kernel source are still two different
things. Why should we allow the precedent and create such a license mess?
The problem is easy to ignore now, but it will possibly hunt us forever.

> This was very much not intended to start a flamewar (and I do apologize if
> anyone was offended by the post), but I think the very real fear of
> oversealous GPL defenders is a large part of the reason why a modified GPL
> was not chosen.

This is simply not true, if the usage terms are clearly defined in
advance, we can easily easily ignore the trolls. Did anyone ever complain
about the libgcc license? I don't think your fear is justified.

bye, Roman

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