On Sun, Feb 16, 2020 at 9:25 AM Igor Gnatenko <ignatenkobrain@xxxxxxxxxxxxxxxxx> wrote: > > In Rust world we package all crates as source code in -devel packages. > Then we use them to build the real applications. > > Some time ago, someone noticed that we don't put licenses of those > -devel packages into a resulting RPM with app which is fair. > > However, I'm not entirely sure how to properly write the License tag. > What should be there if -devel packages have: > > * ASL 2.0 > * ASL 2.0 or Boost > * ASL 2.0 or MIT > * ISC > * MIT > * (MIT or ASL 2.0) and BSD > * Unlicense or MIT > > Is it correct to put License: ISC and MIT and ASL 2.0 and BSD? My understanding is that "effective license" statements generally only apply for binary artifacts or things where there's a clear way to resolve to a simpler situation. Since Rust stuff only has that apply if binary artifacts are produced (when producing executables or binary libraries), in most cases you can't do that. Since Rust packages are normally a pile of source code that people can freely depend on any part of (unless you're compiling a binary), you need to list it all out. So then it gets to be this fun string: > License: ASL 2.0 and (ASL 2.0 or Boost) and (ASL 2.0 or MIT) and ISC and MIT and ((MIT or ASL 2.0) and BSD) and (Unlicense or MIT) Isn't it wonderful? :/ -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ legal mailing list -- legal@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to legal-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/legal@xxxxxxxxxxxxxxxxxxxxxxx
