Pandu Poluan wrote:
I think your statement (quoted below) is slightly incorrect.
The GPL FAQ here: http://www.gnu.org/licenses/gpl-faq.html#LinkingWithGPL
Clearly states:
... you must release your program under a license compatible with the GPL
(more precisely, compatible with one or more GPL versions accepted by all
the rest of the code in the combination that you link).
Granted, "compatible with GPL" does not mean it must be GPL, but it must
carry on the "Freedom" of GPL.
I don't think PCMAV's license is GPL-compatible, as they do not provide
their source code at all.
{p}
On Tue, Aug 12, 2008 at 2:59 AM, Geoff Partridge <geo...@airstream.net.nz>wrote:
If you mix GPL code in with your own code, then yes, you are obligated to
release those modifications sourcecode. However, if your code just links to
GPL code, you are under no such obligation.
Regards,
You are correct Pandu. I'll also note that you can not 'link' to GPL
code via a non-GPL'd app unless 1) the library is LGPL'd, or 2) You have
an exception made by the developers of said app (not just one, but every
developer that retains copyright over code included in said app).
The only way I've seen 3rd party closed source apps use clamav without
violating the license, is to either develop their own client, then use
either TCP or UNIX-socket access to clamd and pass scanning back and
forth that way, or to save the data needing scanning to a temp file,
then executing clamscan/clamdscan on the file, and taking the return
code as a yes/no.
17 messages in net.clamav.lists.clamav-win32Re: [clamav-win32] Question regarding...
