[Nagiosplug-devel] [Nagios-users] Licensing of Official and 3rd Party Plugins

Thomas Guyot-Sionnest thomas at zango.com
Thu Jan 10 16:13:01 CET 2008

Hash: SHA1

Andreas Ericsson wrote:
> Holger Weiss wrote:
>> I thought so, too, but I checked before my other posting and most of
>> Gnulib is actually LGPL'd, despite the headers in the C files:
>> | Many modules are provided dual-license, either GPL or LGPL at your
>> | option.  The headers of files in the lib directory (e.g., lib/error.c)
>> | state GPL for convenience, since the bulk of current gnulib users are
>> | GPL'd programs.  But the files in the modules directory (e.g.,
>> | modules/error) state the true license of each file, and when you use
>> | 'gnulib-tool --lgpl --import <modules>', gnulib-tool either rewrites
>> | the files to have an LGPL header as part of copying them from gnulib
>> | to your project directory, or fails because the modules you requested
>> | were not licensed under LGPL.
>> [ http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=blob_plain;f=COPYING ]
>> AFAICS, we're currently not using any of the GPL-only Gnulib files.
>> Anyway, if you (or others) would like to upgrade to GPLv3, I'm perfectly
>> fine with that.  I just stated my personal preference, but the license
>> question isn't important to me.

Thanks for the clarification, Holger.

I'll check whenever we can --lgpl it.

> For the plugins it won't matter in the slightest which version is used,
> as it isn't a library and so other programs will never have to think
> about it. That will only become an issue if someone tries to use the
> API functions in a GPLv2-only program.

Holger have plans to make a C library similar in functionality to
Nagios::Plugin. Although that would not be an issue either if the
library is lgpl'ed, a discussion about the license of this project
haven't even started...

- --
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the Devel mailing list