Skip to content
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

Fix license #12

Merged
merged 2 commits into from
Jun 10, 2023
Merged

Fix license #12

merged 2 commits into from
Jun 10, 2023

Conversation

michel-slm
Copy link
Contributor

Add license text for MIT, and change the license declaration from MIT AND Apache-2.0 to the more common MIT OR Apache-2.0

Fixes #11

Also rename the previous `LICENSE` file to `LICENSE-APACHE`

```
michel in sha256-rs on  fix-license [?] is 📦 v1.1.3 via 🦀 v1.69.0
⬢ [fedora-toolbox:38] ❯ cargo package --allow-dirty --no-verify
   Packaging sha256 v1.1.3 (/home/michel/src/github/baoyachi/sha256-rs)
    Packaged 12 files, 21.0KiB (7.3KiB compressed)

michel in sha256-rs on  fix-license [?] is 📦 v1.1.3 via 🦀 v1.69.0
⬢ [fedora-toolbox:38] ❯ tar tf target/package/sha256-1.1.3.crate | grep LICENSE
sha256-1.1.3/LICENSE-APACHE
sha256-1.1.3/LICENSE-MIT
```

Signed-off-by: Michel Alexandre Salim <[email protected]>
The convention in Rust crates is to allow the user the choice of either
MIT OR Apache-2.0; requiring both MIT and Apache-2.0 is unusual (and
given the license terms of MIT, is effectively just Apache-2.0 anyway
but requires both license files to be shipped).

Convert from `AND` to `OR`.

Signed-off-by: Michel Alexandre Salim <[email protected]>
@baoyachi baoyachi merged commit 6627dec into baoyachi:master Jun 10, 2023
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 this pull request may close these issues.

License clarification
2 participants