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

Sterling Hughes commented on MYNEWT-29:
---------------------------------------

Hey Justin, 

Removing this one is unfortunately a huge pain.  We depend on 
github.com/spf13/viper, which depends on yaml.v2, which has the LGPL license.

This license is LGPL with an exception for static linking.  This would not be 
too onerous on our users: 

- Our users are releasing products with the Mynewt Operating System, the newt 
build tool is used to create those artifacts, so the actual work product would 
not be affected. 
- The newt build tool would not include any source or APIs from the LGPL 
software, and the package which does depend on this software, does not seem to 
think _THEY_ fall under the LGPL
- I can remove Godeps from our directory (users can use go get to download 
packages), in which case we will not be redistributing the offending license

And then for beta2, we can go ahead and look to replace this yaml parser with a 
better one.  Does this seem reasonable?

> 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)

Reply via email to