License for packaging#6
Conversation
|
I was also pointed to this discussion which seems to suggest that the generated files would have to have the |
|
It is |
|
As far as I can tell, the situation here is very similar to the unicode-ident crate: https://crates.io/crates/unicode-ident See also dtolnay/unicode-ident#9 where See also https://github.com/unicode-rs/unicode-xid/pull/32/files for a similar request for a different unicode-rs crate. |
|
It was pointed out downstream that the license text here is |
LecrisUT
left a comment
There was a problem hiding this comment.
Thanks, what a (un?)fortunate chain of events. @Manishearth, would you consider this PR?
I am trying to package this project for Fedora 1 and we've encountered ambiguous license issue. The suggestion was that it should be licensed under
(MIT OR Apache-2.0) AND Unicode-DFS-2016due toscripts/unicode.pyThere could be another possibility to simply exclude
scripts/*from crate, but I am not sure if the generated code is under the same license Unicode license or not.Footnotes
https://bugzilla.redhat.com/show_bug.cgi?id=2279853 ↩