Please support including licenses for the standard libraries

[joshtriplett]

In addition to the licenses of dependencies, please consider also including the licenses that apply to std, core, libc/libm, compiler_builtins, and similar. This would help people trying to provide documentation of the software they bundle, for license compliance.

[Nemo157]

Makes a lot of sense. It looks like the text at least is available under share/doc/rust in the toolchain. Although, that doesn’t appear to have any mention of hashbrown and other third-party crates?

Working out the relevant crates will also be interesting, determining if std is linked is complex, and I have very little idea if it is even possible to tell whether other crates from the sysroot are relevant.

If sysroot-aware/custom-std Cargo was anywhere near ready then that could hopefully avoid a lot of this by treating them as normal crates. Although that does give me one idea, the rust-src component could be required and the Cargo.toml from there read somehow to get the information.

[joshtriplett]

On November 26, 2019 1:15:52 PM PST, Nemo157 ***@***.***> wrote: Makes a lot of sense. It looks like the text at least is available under `share/doc/rust` in the toolchain. Although, that doesn’t appear to have any mention of `hashbrown` and other third-party crates?> > Working out the relevant crates will also be interesting, determining if `std` is linked is complex, and I have very little idea if is even possible to tell whether other crates from the sysroot are relevant.> > If sysroot-aware/custom-std Cargo was anywhere near ready then that could hopefully avoid a lot of this by treating them as normal crates. Although that does give me one idea, the `rust-src` component could be required and the `Cargo.toml` from there read somehow to get the information.> > -- > You are receiving this because you authored the thread.> Reply to this email directly or view it on GitHub:> #63 (comment)

The complexity is precisely the reason we should try to figure this out. :) And yes, we may need to update some third-party licenses.