Skip to content

Conversation

@a-wai
Copy link

@a-wai a-wai commented Jan 29, 2025

As the license file is present at the root of the repository, it isn't part of any crate on crates.io, as those lie in subfolders. Ensure this file is published by telling cargo where to find it.

As the license file is present at the root of the repository, it isn't
part of any crate on crates.io, as those lie in subfolders. Ensure this
file is published by telling cargo where to find it.
Copy link

@10ne1 10ne1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gentle ping?

@musicinmybrain
Copy link

musicinmybrain commented May 18, 2025

This does appear to work (tested with cargo publish --dry-run), but it does produce a warning from cargo:

warning: only one of `license` or `license-file` is necessary
`license` should be used if the package license can be expressed with a standard SPDX expression.
`license-file` should be used if the package uses a non-standard license.
See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.

A widely-used alternative approach would be to use symbolic links to the top-level license file, as in #113.

@a-wai
Copy link
Author

a-wai commented May 19, 2025

#113 looks better indeed, closing this one. Thanks!

@a-wai a-wai closed this May 19, 2025
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.

3 participants