New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LGPL m4/ax_code_coverage.m4 conflicts with ISC license of curl source package #3497

Closed
wrowe opened this Issue Jan 24, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@wrowe
Copy link

wrowe commented Jan 24, 2019

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.

bagder added a commit that referenced this issue Jan 25, 2019

configure: rewrite --enable-code-coverage
The previously used ax_code_coverage.m4 is not license compatible and
must not be used.

Reported-by: William A. Rowe Jr
Fixes #3497
@bagder

This comment has been minimized.

Copy link
Member

bagder commented Jan 25, 2019

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.

@bagder bagder closed this in 179311e Jan 25, 2019

@bagder

This comment has been minimized.

Copy link
Member

bagder commented Jan 25, 2019

Thanks for the report. Issued fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment