Re: Yikes! License problem with SE library classes.

I 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).

For version 0.2.2 of "Amber for Parrot"
http://xamber.org/index.html
that I released today I have, in addition to the Gnu GPL, licensed the
software under the Eiffel Forum License v2 to the extent that is needed
to allow me to distribute the C-package generated by SmartEiffel.

I would still appreciate a resolution of the license problem that arises
when using SmartEiffel to produce a C-package from a GPL application
combined with SmartEiffel's non-GPL libraries.

Regards,
Roger Browne