https://bugzilla.redhat.com/show_bug.cgi?id=2247562
--- Comment #12 from Ben Beasley <[email protected]> --- I suppose that for a REUSE project like this, you could restore the BR on reuse and do something like %build # Produce an automated breakdown of licenses in source files. Some of these # files do not contribute to the licenses of the binary RPMs. reuse spdx | tee LICENSES.spdx … %files %license LICENSES/* LICENSES.spdx and that would satisfy the requirement for a breakdown of licenses, but the disadvantages are: - the tool has no way to tell which files do or do not contribute to the licenses of the binary RPMs - the tool has no way to tell which CC0-1.0 are “code” vs. “content,” nor which “code” files are allowed under the exception for trivial code in REUSE projects - the tool has no way to infer which license is intended for the .po files (really, upstream should ideally make this explicit) so as the package is updated with new files, you’re still going to have to do some manual analysis to determine what the License expression should be and whether everything is indeed still allowable in Fedora. -- 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=2247562 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202247562%23c12 -- _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
