Publish crate with license files

[afq984]

Hi, I would like to import the dasp_sample crate for use in AOSP and AOSP importer checks for license files that are bundled along with the crate that was downloaded from crates.io.

I manually inspected https://crates.io/api/v1/crates/dasp_sample/0.11.0/download and it indeed does not contain the LICENSE-MIT and LICENSE-APACHE files.

Could a new release be made to include the license text? Thank you!

[est31]

cc @mitchmindtree on this, as they authored most of the code.

In general, the license files are already present in the git repo, they are just not in the particular crate folders. We'd need to copy them over I guess.

[afq984]

I just did a quick test and symlinking from ../LICENSE-APACHE and ../LICENSE-MIT does work

[est31]

#188 is merged now, now only a release is missing.

[afq984]

Hi, just checking again if a new release can be published, thanks!

[damaestro]

License file missing from published crate

When dasp_sample is published to crates.io, the resulting .crate archive does not contain a LICENSE, LICENSE-MIT, or LICENSE-APACHE file.

Why this matters

Linux distributions (Fedora, openSUSE, Debian, etc.) package Rust crates as system packages. Fedora packaging policy requires that every package ships the full license text — see Fedora Licensing Guidelines § License Text. It cannot simply reference a URL or rely on license = "..." in Cargo.toml. When a crate does not bundle a license file, packagers are forced to either:

• Download the license file out-of-band from the GitHub repository (fragile, and breaks if the repo moves or branch names change), or
• Synthesize a license file from a template (legally questionable), or
• Block the package entirely until this is fixed.

How to fix

Add the license file(s) to the crate by including them in Cargo.toml's include list (or by removing an overly restrictive include that excludes them):

[package]
# ...
license = "MIT OR Apache-2.0"

include = [
    "src/**",
    "LICENSE-MIT",
    "LICENSE-APACHE",
    "README.md",
]

If your Cargo.toml does not have an explicit include list, Cargo will include LICENSE* files automatically — so the fix may be as simple as ensuring the license files are present in the crate subdirectory within this workspace.

Verification

After publishing a new version you can verify the license file is present by running:

tar tf ~/.cargo/registry/cache/index.crates.io-*/dasp_sample-*.crate | grep -i license

Thank you for maintaining this crate!