Re: Yikes! License problem with SE library classes.

Le Vendredi 1 Juillet 2005 17:45, Cyril ADRIAN a écrit :
> Hello,
>
> Roger Browne wrote:
> >Here's the problem: the C-package is a derived work that includes both
> >my source code (GPL'd) and the SmartEiffel library code. Therefore, I
> >need to offer the entire source code under the GPL. But I can't do that,
> >because the SmartEiffel library license is not GPL-compatible (for
> >example, it imposes a requirement that a change log must be added).
>
> Thanks for bring this to our attention. I, for one, was not aware of the
> problem.

Neither was I.

> Would removing this requirement be enough? Or are there other
> incompatibilities?
>
> Should we dual-licence the library? (a la QT maybe?)
>
> You know why the library is not GPL'ed: we want our product to be
> available *both* for open source projects and industrial projects.

Why not just use permissive, gpl-compatible license ? The MIT/X license 
(http://www.opensource.org/licenses/mit-license.html) and the Eiffel Forum 
License v2 suggested by Roger 
(http://www.opensource.org/licenses/ver2_eiffel.php) come to mind. Both are 
rather well-known (at least in Eiffel circles) and OSI-approved.