https://bugzilla.redhat.com/show_bug.cgi?id=1983877
--- Comment #4 from Fabio Valentini <decatho...@gmail.com> ---
There is cargo-license, but it obviously does not take into account any of our
downstream patches or modifications.
I usually use this bash script inside the mock chroot after running a build
with "--without check":
for i in $(rpm -qa | grep "rust-.*-devel"); do
rpm -q $i --qf "%{LICENSE}\n";
done | sort | uniq
It gives you a list of all licenses of installed rust-foo-devel packages in the
buildroot. From those you can construct the "effective" license of the
subpackage that contains the binary.
Alternatively, if you want a list of all Rust crates and their licenses in
detail, you can install dnf-utils into the mock chroot and run something like:
dnf repoquery --cacheonly "rust-*-devel" --installed --qf "# %{LICENSE}:
%{source_name} %{version}"
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=1983877
_______________________________________________
package-review mailing list -- package-review@lists.fedoraproject.org
To unsubscribe send an email to package-review-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/package-review@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
