On Fri, Aug 2, 2024 at 2:01 PM Vít Ondruch <vondr...@redhat.com> wrote:
>
> Dne 01. 08. 24 v 15:47 Neal Gompa napsal(a):
> > Yes, because it's relatively new and it's not that important most of
> > the time. It was added in RPM 4.18.
>
> Well, unless it is in guidelines, I don't think it will be used.

Rust packages generated with rust2rpm use it when it makes sense to
differentiate License of the built packages vs. license of the project
sources.
This is the case for packages where <source package name> == <built
package name>, so usually for large Rust projects packaged from $FORGE
tarballs instead of from sources hosted on crates.io.
For projects packaged from crates.io, the source package name
(rust-<crate>) and built package name (usually <crate>) are already
always different, so using SourceLicense is not necessary to
differentiate license of the package sources and license of the
contents of the built package.

And support for SourceLicense is even getting backported to RHEL 9 -
one less reason *not* to use this :)
https://issues.redhat.com/browse/RHEL-28798

Fabio
-- 
_______________________________________________
legal mailing list -- legal@lists.fedoraproject.org
To unsubscribe send an email to legal-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/legal@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to