https://bugzilla.redhat.com/show_bug.cgi?id=2165399
--- Comment #28 from Carl George 🤠<c...@redhat.com> --- What I've done in cases like that is: - extract the text of the license from the source file and include it in a text file - list that text file as an additional Source in the spec file - include a comment indicating what source file the license text was extracted from - copy that additional source file to the build dir during %prep, so it can be picked up by %license easily That fulfills the license requirement to include the copyright notice in distributed copies. It also aligns with the packaging guidance for what to do when upstreams don't include the license text at all. > Include a copy of what they believe the license text is intended to be, as > part of the Fedora package in %license, in order to remain in compliance. https://docs.fedoraproject.org/en-US/packaging-guidelines/LicensingGuidelines/#_license_text -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2165399 _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
