I'm working on packaging bon / bon-macros for Fedora Linux, they're now pulled in via GNOME → glycin → jpegxl-rs → bon, and noticed that the published crates don't contain copies of the Apache-2.0 and MIT license texts.
Both the Apache-2.0 and MIT license terms require the (re)distributed sources contain a copy of the license text, which is currently not the case for the crates redistributed via crates.io (and by extension, problematic for Linux distributions that want / need to include the crates).
Assuming you run "cargo publish" on any OS that supports symbolic links properly (i.e. not Windows in the default configuration), adding symbolic links in workspace members that point at the two LICENSE-* files should be enough for this to work - cargo publish resolves symbolic links when preparing the archive for publishing and includes the actual files, not symlinks.
I'm working on packaging bon / bon-macros for Fedora Linux, they're now pulled in via GNOME → glycin → jpegxl-rs → bon, and noticed that the published crates don't contain copies of the Apache-2.0 and MIT license texts.
Both the Apache-2.0 and MIT license terms require the (re)distributed sources contain a copy of the license text, which is currently not the case for the crates redistributed via crates.io (and by extension, problematic for Linux distributions that want / need to include the crates).
Assuming you run "cargo publish" on any OS that supports symbolic links properly (i.e. not Windows in the default configuration), adding symbolic links in workspace members that point at the two
LICENSE-*files should be enough for this to work -cargo publishresolves symbolic links when preparing the archive for publishing and includes the actual files, not symlinks.