LGPL m4/ax_code_coverage.m4 conflicts with ISC license of curl source package · Issue #3497 · curl/curl · GitHub
Skip to content 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 LGPL m4/ax_code_coverage.m4 conflicts with ISC license of curl source package #3497 New issue Copy link New issue Copy link Closed Closed LGPL m4/ax_code_coverage.m4 conflicts with ISC license of curl source package #3497 Copy link Labels build documentation Description wrowe opened on Jan 24, 2019 Issue body actions The file m4/ax_code_coverage.m4 was introduced to Curl two years ago; f6e0f45 and distributed in source bundles since 7.54.1.
It is incorporated into the project's ./configure script as part of the automake/autoconf preparation. This renders the source code package contents including generated ./configure incompatible with the ISC license from COPYING, as portions of ./configure are then under LGPL 2.1 terms. The terms of m4/ax_code_coverage.m4 license further place the burden on Curl to share the LGPL 2.1 document when distributing this macro.
This macro, as opposed to most autoconf/automake macros, failed to offer the following licensing exception which is used to make usable automake and autoconf for ISC, BSD and similarly licensed works; # As a special exception, the respective Autoconf Macro's copyright owner # gives unlimited permission to copy, distribute and modify the configure # scripts that are the output of Autoconf when processing the Macro. You # need not follow the terms of the GNU General Public License when using # or distributing such scripts, even though portions of the text of the # Macro appear in them.
The GNU General Public License (GPL) does govern # all other use of the material that constitutes the Autoconf Macro. I have confirmed the current sources contain the same defect; http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=blob_plain;f=m4/ax_code_coverage.m4 If the 6 authors agreed on adding the clause, they could elect to relicense. In the interim, I believe the patch needs to be reverted. Activity bagder added a commit that references this issue on Jan 25, 2019 configure: rewrite --enable-code-coverage This issue will close once commit ebd426d is merged into the 'master' branch. ebd426d bagder added build documentation on Jan 25, 2019 bagder commented on Jan 25, 2019 bagder on Jan 25, 2019 Member More actions I agree with the conclusions and as a consequence I'm doing a rewrite and simplification of that logic to remove the dependency without losing functionality.
Reacted by Marcel Raad and William A Rowe Jr bagder closed this as completed in 179311e on Jan 25, 2019 bagder commented on Jan 25, 2019 bagder on Jan 25, 2019 Member More actions Thanks for the report. Issued fixed! Reacted by William A Rowe Jr lock locked as resolved and limited conversation to collaborators on Apr 26, 2019 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Metadata Metadata Assignees No one assigned Labels build documentation Type No type Projects No projects Milestone No milestone Relationships None yet Development No branches or pull requests Issue actions You can’t perform that action at this time.