On Tue, 19 Oct 2010 16:05:51 -0400 Justin Seyster <jrs...@gmail.com> 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 definitive and legal answer should be asked to expensive lawyers after showing them http://www.gnu.org/licenses/gcc-exception.html I am not a lawyer (and not a US citizen), I don't even understand all the details of GPLv3 and my naive answer is that plugin which are GPLv3 are ok (in particular when they are used to compile GPL software). Perhaps even any plugin with a licence compatible with GPLv3 is ok, but I cannot explain what that is meaning :-) And that also applies to anything dlopen-ed by a GCC plugin or a GCC branch such as a MELT module, see http://gcc-melt.org/ or http://gcc.gnu.org/wiki/MELT or come hear my MELT tutorial at the GCC Summit next week :) So my naive advice to you is to release your code as GPLv3. It could happen that I am wrong. So let just say that it is my wish. The other advantage of GPLv3 plugins is that they are playing the rules wanted by most GCC contributors, and that GCC maintainers could have a glance inside them. I might be happy being able to do that. Cheers. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mine, sont seulement les miennes} ***
