Skip to content

Install materials to comply with upstream licenses #656

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
brson opened this issue Oct 2, 2014 · 2 comments · Fixed by #659
Closed

Install materials to comply with upstream licenses #656

brson opened this issue Oct 2, 2014 · 2 comments · Fixed by #659

Comments

@brson
Copy link
Contributor

brson commented Oct 2, 2014

Cargo packages and distributes as binaries many upstream components. To comply with those licenses we need to do some things. I suggest:

  • In README.md put the text "This product includes software developed
    by the OpenSSL Project for use in the OpenSSL Toolkit
    (http://www.openssl.org/)", to comply with clause 6 of the OpenSSL
    license. It doesn't actually matter to say this for the source
    distribution, but it does in the binary distribution.
  • Write (or generate) a LICENSE-THIRD-PARTY (to be distinct from the
    main Cargo license file) file that simply concatenates all the
    unique licenses of the dependencies. It's most crucial that this
    contains the GPL2 with runtime exception from libgit2. This does not
    need to be distributed with the source, but does with the binaries.
  • Install the README and all license files to ${prefix}/share/doc/cargo.

cc rust-lang/rust#17690

@brson brson changed the title Install materials to comply with downstream licenses Install materials to comply with upstream licenses Oct 2, 2014
@brson
Copy link
Contributor Author

brson commented Oct 2, 2014

Here's the current list of upstream components:

Third-party software that cargo links to:

Rust ecosystem software Cargo links to that is not part of the Rust project

The ones with undeclared licenses are all controlled by people we know, and will be whatever we ask them to be (likely MIT/ASL2).

First-party software that cargo links to

@alexcrichton
Copy link
Member

All of my own dependencies are now MIT/ASL2, and upstream curl-rust (which our branch is based on) is MIT, and curl-sys falls under that umbrella. This means that rust software is at least MIT, except docopt, which is public domain.

alexcrichton added a commit to alexcrichton/cargo that referenced this issue Oct 2, 2014
This follows rust-lang#656 by mentioning OpenSSL in the README, as well as install all
license files on installation. A hand-generated LICENSE-THIRD-PARTY is also
included.

Closes rust-lang#656

This also approaches rust-lang#657 by mentioning that we have GPL software in the README.
Cargo will hopefully support a more complete "all source" distribution in the
future, but at this time there is not an easy way to generate a complete source
tarball via cargo.
bors added a commit that referenced this issue Oct 2, 2014
This follows #656 by mentioning OpenSSL in the README, as well as install all
license files on installation. A hand-generated LICENSE-THIRD-PARTY is also
included.

Closes #656

This also approaches #657 by mentioning that we have GPL software in the README.
Cargo will hopefully support a more complete "all source" distribution in the
future, but at this time there is not an easy way to generate a complete source
tarball via cargo.
@bors bors closed this as completed in #659 Oct 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants