Hi,
I'm maintaining apcupsd package. Apcupsd itself is under GPLv2 license.
Apcupsd daemon in this package is linked against a few libraries including net-snmp and openssl.
licenses are (based on License tag in rpm): OpenSSL : OpenSSL net-snmp : BSD and MIT
I'd like to know answers for these questions:
1) Is apcupsd allowed to link against openssl since openssl seems to be incompatible with GPLv2? [1]
2) Because net-snmp itself is linked against openssl, should not its license in fact be BSD and MIT and OpenSSL?
3) If apcupsd is not allowed to link against openssl, is it allowed to link against net-snmp which is linked against openssl?
Cheers, Michal Hlavinka
[1] http://gplv3.fsf.org/wiki/index.php/Compatible_licenses#GPLv2- incompatible_licenses
"MH" == Michal Hlavinka mhlavink@redhat.com writes:
MH> 1) Is apcupsd allowed to link against openssl since openssl seems MH> to be incompatible with GPLv2? [1]
Not without an exception.
MH> 2) Because net-snmp itself is linked against openssl, should not MH> its license in fact be BSD and MIT and OpenSSL?
Not unless it's statically linked or somehow includes the actual openssl binary files in the package.
MH> 3) If apcupsd is not allowed to link against openssl, is it MH> allowed to link against net-snmp which is linked against openssl?
That's probably a legal question, but I'd say no.
- J<