GPLv3 pains start now

rockbox Yeah, Rockbox ships as a GPLv2 licensed package, without the "or later" option for users to switch license at will. This has been all fine and dandy for a long time and Rockbox includes source from a busload of different other projects, licensed as GPLv2 and BSD etc.

Now, some of the projects Rockbox uses or wants to use are slowly turning GPLv3. First out being espeak, and the corresponding Rockbox patch for using it.

GPLv2 and GPLv3 are not compatible. We cannot ship binaries built with a mix of these licenses.

So, we're now starting to see the real-world effects of the GPLv3 license. Slowly some projects are going v3, and we (as in the Rockbox project) must remain with their older v2 sources until we take the jump (more or less forced) to v3 - only to then have the reversed situation as then we can't use projects that are licensed strictly GPLv2 (without the "or later")...

Sigh. The world is a complicated place.

One thought on “GPLv3 pains start now”

  1. Yes, some people clearly do not understand that this whole GPLv3 debacle will only _hurt_ the OS movement by hampering development.

Comments are closed.