Linked by Thom Holwerda on Thu 2nd Feb 2006 21:15 UTC
GNU, GPL, Open Source Linus Torvalds, father of the Linux kernel, has fleshed out his unhappiness with GPLv3 in three recent posts on the Linux Kernel Mailing List. Torvalds previously stated that the kernel will remain under the licensing terms of GPLv2. Yesterday, Torvalds offered his opinion as to where the battle over DRM should take place.
Thread beginning with comment 92232
To view parent comment, click here.
To read all comments associated with this story, please click here.
ben_dash
Member since:
2005-10-13

May I be the first to point out that you are wrong.

If you link your program or library to a GPL library you do NOT have to release your code as GPL.

Do you seriously think that everything that links to libgcc has to release their source code as GPL???

http://bensqanda.blogspot.com

Reply Parent Score: 2

Wrawrat Member since:
2005-06-30

Actually, he is right. You are now allowed to link a GPL library with proprietary code. Well, you can, but you cannot distribute the work legally. Hence why the LGPL exists. It got a special provision for linking.

As for gcc, it's a compiler, not a library!

Reply Parent Score: 5

ben_dash Member since:
2005-10-13

I meant the lgpl libc, however, libgcc is actually a library it's in my /lib ;-)

You got me though, I was being too general, I said GPL when I meant LGPL. We were talking about libraries after all and I didn't proof read...

Reply Parent Score: 1

teprrr Member since:
2005-07-06

Um, it's always been allowed to link against GPL library when you don't redistribute your software, no?

And libgcc is a library, at least according to gnu.org.

Reply Parent Score: 1

ben_dash Member since:
2005-10-13

Note to self; proof read before you post and don't type GPL when you're obviously talking about libraries and LGPL ;-)

Reply Parent Score: 2

ben_dash Member since:
2005-10-13

I obviously mean LGPL ;-) sorry about that!

Reply Parent Score: 1