You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 'pki-tps' package contains the original 'tpsclient' which is based upon software which required the LGPL license (as it is comprised of native-based code related to the original pki-tps Apache plug-in), and a newly rewritten java-based Tomcat implementation of 'pki-tps'.
Do we need to carry both the LGPL license for 'tpsclient' as well as the GPL license for 'pki-tps'?
To which legal responded:
It doesn't matter too much but I guess for simplification I would suggest updating
the license of tpsclient to GPL. LGPLv2.1 explicitly contemplates that such license
migration from LGPL to GPL may be done.
The text was updated successfully, but these errors were encountered:
This issue was migrated from Pagure Issue #1547. Originally filed by mharmsen (@mharmsen) on 2015-08-07 01:21:57:
The 'pki-tps' package contains the original 'tpsclient' which is based upon software which required the LGPL license (as it is comprised of native-based code related to the original pki-tps Apache plug-in), and a newly rewritten java-based Tomcat implementation of 'pki-tps'.
To which legal responded:
The text was updated successfully, but these errors were encountered: