[ 
https://issues.apache.org/jira/browse/THRIFT-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18112856#comment-18112856
 ] 

Sylwester Lachiewicz commented on THRIFT-6205:
----------------------------------------------

[PR #3828|https://github.com/apache/thrift/pull/3828] removes both blocks and 
the now-unreferenced {{doc/licenses/otp-base-license.txt}}.

> Remove the stale MIT attribution for the removed Erlang makefile from LICENSE
> -----------------------------------------------------------------------------
>
>                 Key: THRIFT-6205
>                 URL: https://issues.apache.org/jira/browse/THRIFT-6205
>             Project: Thrift
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Sylwester Lachiewicz
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> LICENSE carries an MIT attribution for {{lib/erl/src/Makefile.am}}:
> {noformat}
> --------------------------------------------------
> Portions of the following files are licensed under the MIT License:
>   lib/erl/src/Makefile.am
> Please see doc/otp-base-license.txt for the full terms of this license.
> {noformat}
> That file was removed by THRIFT-892 when the Erlang library moved to rebar, 
> so the entry now attributes a third-party licence to nothing the distribution 
> ships. The path it cites is wrong as well: the text lives at 
> {{doc/licenses/otp-base-license.txt}}.
> {{debian/copyright}} carries the same block naming {{lib/erl/Makefile.am}} 
> instead. That file exists but has always carried the standard ASF header, so 
> the MIT claim never applied to it. THRIFT-5196 asked which licence governs 
> the Erlang makefile; the answer is Apache 2.0, and this stale pair is what 
> made the question ambiguous.
> No otp-base derived content remains anywhere in the tree, which leaves 
> {{doc/licenses/otp-base-license.txt}} unreferenced once both blocks go.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to