Issue #41 resolved


GPL licenses are viewed as less business friendly. I am wondering is you would perhaps consider relicensing under ASL 2.0 which is viewed more business friendly.


Comments (4)

  1. Albert Graef

    Hi Suminda,

    first, Pure is an open-source project and I want to encourage source contributions. The ASL and similar permissive licenses might work for Apache and other high-profile projects which already have lots of contributors, but often they aren't very effective for smaller open-source projects.

    That said, in fact most of Pure is not licensed under the GPL, but under the LESSER GPL (LGPL). The LGPL is not as liberal as the ASL, but it certainly makes it feasible to link proprietary software against the Pure runtime library or distribute compiled Pure programs together with the required runtime libraries under a commercial license. (Most of the add-on libraries also use either the LGPL or a permissive license like the BSDL, usually following the license model of the 3rd party libraries they interface to.) It is true that the LGPL poses some limitations, but these are there to ensure that improvements to the Pure runtime are contributed back, and that users don't loose the right to use whatever version of the Pure runtime they want/need.

    The only notable exception to this is the interpreter main program (which needs to be under the GPL as it gets linked against the GNU readline library). But this is only a very small part of the Pure system, and you could easily write your own interpreter frontend if this is a major impediment. In fact, there's ready-made and BSDL-licensed code in the Pure distribution which can serve as a drop-in replacement for the default frontend in

  2. Albert Graef

    Ok, so I laid out my reasons for preferring the LGPL above, but that doesn't mean that I want to preclude any further discussion of this issue, so I'm leaving this open. If there are license issues which make it rather impossible to develop commercial software using Pure, I certainly want to hear about it, so that we can find ways to resolve those issues.

  3. Log in to comment