Licensing question

[Mears]

I'm developing an application for a government customer and am
interested in leveraging Winpdb. However, the software I am
developing cannot be released under the GPL license due to both
employer and customer requirements. Because of this, I had planned to
write PDB extensions. I've since discovered that two different Python
editor projects are using winpdb (one of which has advertised on this
group), but are not using GPL. It appears that they have skirted
around the copyleft provisions of GPL by making Winpdb an optional
plugin that can be disabled. I've noticed that others have taken a
similar approach to use GPL modules with non-GPL code.

Is this legitimate? Would I run afoul of GPL requirements if I bundle
winpdb with my application and give users the option of disabling it.
To be clear, I would be importing winpdb/rpdb in my code, but that
code would be a plugin to the main application that could be
disabled. Would I be forced to GPL the plugin code that interfaces
with winpdb?

[Mike Rans]

Editra does use GPL. The WxWindows licence which it uses says:
This library is free software; you can redistribute it and/or modify
it
under the terms of the GNU Library General Public Licence as
published by
the Free Software Foundation; either version 2 of the Licence, or
(at
your option) any later version.

[Nir Aides]

Hi Mike,

The license excerpt you have pasted is actually of LGPL, not GPL.
Code that includes Winpdb needs to be distributed as GPL.

Nir

> --
> You received this message because you are subscribed to the Google Groups "Winpdb" group.
> To post to this group, send email to win...@googlegroups.com.
> To unsubscribe from this group, send email to winpdb+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/winpdb?hl=en.
>
>