Linked by Thom Holwerda on Sun 14th Nov 2010 22:41 UTC
Permalink for comment 450054
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2009-08-11
Hold on, what's the problem here? What Google did is perfectly legal: There is nothing in the GPL that says you can't decompile GPL'ed binaries or redistribute said decompiled code; it's still licensed under the GPL.
I would also mention that putting code in the same source tree doesn't make all of the code part of the same work. For example, in one of my projects I have rhino.jar and closure-compiler.jar in my build directory. Rhino is MPL/GPL'd and Closure Compiler is Apache Licensed but my project is New BSD licensed; the same goes for jQuery. Am I infringing on Mozilla and Google's copyrights to their respective works? No. These tools are in my source tree for testing and minifying, nothing else.