News for hackers. Stuff that matters.
Re:An analysis of GPLed code in Thesis by mseebach on Thursday July 15, 2010 @02:40PM (#1518682)
That's not at all simple. The corollary of that statement is "if you don't like the GPL, don't develop applications for GNU/Linux".
Re:An analysis of GPLed code in Thesis by pmjordan on Thursday July 15, 2010 @03:13PM (#1518806)
If you dislike it enough not to use any GPLed software, sure. The GPL specifically distinguishes between code running as part of the same "application" or not. In fact, the kernel itself has a clarification.

GCC itself is GPL, but its libraries (along with glibc) have an exception that permits linking against non-GPL software.

Re:An analysis of GPLed code in Thesis by icey on Thursday July 15, 2010 @03:22PM (#1518844)
WordPress states explicitly that it considers the PHP portion of themes to be GPLed. Seems pretty simple to me.
Re:An analysis of GPLed code in Thesis by slantyyz on Thursday July 15, 2010 @05:58PM (#1519378)
WordPress states explicitly that it considers the PHP portion of themes to be GPLed.

That they consider it a derivative work is their -legal opinion-. Remember their license still doesn't supercede local laws and a court could invalidate Wordpress' legal opinion of what a derivative work is.

Re:An analysis of GPLed code in Thesis by stoney on Thursday July 15, 2010 @06:55PM (#1519549)
Furthermore, it doesn't matter what WordPress considers to be GPLed or not, what matters is what it says in the license.