Justin Seyster writes:
> Thanks for this advice. The link to the GCC Exception was especially helpful.
>
> The trick here is that I'm actually releasing a library designed to be
> linked into plug-ins. I want the library itself to be copyleft but
> for plug-in authors to retain any licensing fl
Thanks for this advice. The link to the GCC Exception was especially helpful.
The trick here is that I'm actually releasing a library designed to be
linked into plug-ins. I want the library itself to be copyleft but
for plug-in authors to retain any licensing flexibility that they
would have whe
Justin Seyster writes:
> I'm getting ready to release plug-in code, and I want to have a very
> clear idea about licensing before I release. I'm leaning towards
> releasing everything as GPLv3, but I do want to know exactly what is
> and isn't allowed.
GPLv3 is fine.
> I know this issue was de
On Tue, 19 Oct 2010 16:05:51 -0400
Justin Seyster wrote:
> I'm getting ready to release plug-in code, and I want to have a very
> clear idea about licensing before I release. I'm leaning towards
> releasing everything as GPLv3, but I do want to know exactly what is
> and isn't allowed.
A defini
