[
https://issues.apache.org/jira/browse/MYNEWT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146315#comment-15146315
]
Justin Mclean commented on MYNEWT-29:
-------------------------------------
Yep it a pain but necessary. The LPGL puts restrictions on distribution which
are not compatible with the Apache license. We would need to ask on the
incubator list if it was OK it make a release first and remove the dependancy
later. The LGPL code will need to be removed from the repo.
"The LGPL is ineligible primarily due to the restrictions it places on larger
works, violating the third license criterion. Therefore, LGPL-licensed works
must not be included in Apache products."
http://www.apache.org/legal/resolved.html#category-x
But the main issue is we would be unable to distribute a release even if the
LGPL code is in the binary or not.
http://www.apache.org/legal/resolved.html#optional
There are a few build tools that are allowed in a release:
http://www.apache.org/legal/resolved.html#build-tools
It's a possibility may fall into a grey area i.e. it's usually assumed that the
user may be using non AL v2 tools (i.e. Java) to compile the software but
that would probably need to be discussed on the legal list.
Also this may provide some insight (it's rather long however):
https://issues.apache.org/jira/browse/LEGAL-192
> Fixup License Headers
> ---------------------
>
> Key: MYNEWT-29
> URL: https://issues.apache.org/jira/browse/MYNEWT-29
> Project: Mynewt
> Issue Type: Task
> Reporter: Sterling Hughes
> Assignee: Justin Mclean
> Fix For: v0_8_0_beta1
>
>
> - Rename license headers from Runtime to ASF license headers
> - Remove ASF license headers from 3rd party files
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
