Skip to content
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

fuzzer: Correct the LICENSE #184

Merged
merged 1 commit into from
Sep 19, 2019
Merged

fuzzer: Correct the LICENSE #184

merged 1 commit into from
Sep 19, 2019

Conversation

chfast
Copy link
Member

@chfast chfast commented Sep 18, 2019

Change the license of evmone-fuzzer from Apache 2.0 to GPL 3.0.
This is required because evmone-fuzzer "links to" aleth-interpreter (GPL 3.0).

@axic
Copy link
Member

axic commented Sep 18, 2019

This is required because evmone-fuzzer "links to" aleth-interpreter (GPL 3.0).

It is not required, Apache 2.0 is compatible with GPL 3.0. This source still can be Apache licensed, but the resulting linked binary will be GPL 3.0.

@chfast
Copy link
Member Author

chfast commented Sep 18, 2019

It is not required, Apache 2.0 is compatible with GPL 3.0. This source still can be Apache licensed, but the resulting linked binary will be GPL 3.0.

This seems right. Anyway, you suggest to remove changes in sources, but leave README and LICENSE?

@axic
Copy link
Member

axic commented Sep 18, 2019

Anyway, you suggest to remove changes in sources, but leave README and LICENSE?

To simplify licensing in this repository I would suggest to keep everything under the same license (Apache 2.0) and mention in the fuzzer README that since aleth-interpreter is statically linked, the resulting fuzzer binary falls under the terms of GPL-3.0.

@chfast
Copy link
Member Author

chfast commented Sep 18, 2019

It does not make sense yet. The evmone-fuzzer being a aleth-interepreter derived work, its source code must be released under GPL (Apache is compatible with GPL only in the other direction).

@axic
Copy link
Member

axic commented Sep 18, 2019

The evmone-fuzzer being a aleth-interepreter derived work

Well it is a debatable case, hence why LGPL was created. The best would just linking dynamically through EVMC to both aleth-interpreter and evmone.

The README file for evmone-fuzzer subproject explains the licensing when building with aleth-interpreter.
@chfast
Copy link
Member Author

chfast commented Sep 19, 2019

Better now?

@codecov-io
Copy link

Codecov Report

Merging #184 into master will increase coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #184      +/-   ##
==========================================
+ Coverage   99.52%   99.64%   +0.11%     
==========================================
  Files           5        5              
  Lines         839      839              
  Branches      109      109              
==========================================
+ Hits          835      836       +1     
+ Misses          1        0       -1     
  Partials        3        3

@axic
Copy link
Member

axic commented Sep 19, 2019

I think the argument here is that you link against EVMC which is Apache-2.0 and you are a "derived work" (but don't think Apache defines that as strictly as GPL) of that. Aleth-Interpreter also just implements that.

@chfast
Copy link
Member Author

chfast commented Sep 19, 2019

I don't care much about it. I just didn't want to totally ignore the issue.

@chfast chfast merged commit e671ae7 into master Sep 19, 2019
@chfast chfast deleted the fuzzer_license branch September 19, 2019 10:46
jwasinger pushed a commit to jwasinger/evmone that referenced this pull request Apr 27, 2021
Rename EVMC_LATEST_REVISION to EVMC_MAX_REVISION
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants