On Mon, Oct 30, 2023 at 12:01:54PM +0100, Fabio Valentini wrote: > On Mon, Oct 30, 2023 at 10:56 AM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote: > > > > The act of copying content from one RPM build dependancy package into > > the RPM output is a more general problem that Doxygen, with static > > linking being the poster-child for it. This static linking happens > > continually with some languages like Rust/Go/Ocaml, and AFAICT the > > license tags implications have been essentially ignored. > > This is just not true, especially for Rust. We do our best to > accurately reflect statically linked dependencies, and we have helper > scripts / macros to determine *which* dependencies are actually linked > into the final binaries, and which are only needed at build-time. And > I also do similar things for the one Go package I maintain. My bad, I see we did actually call out static linking implications on licenses for Rust in particular: https://docs.fedoraproject.org/en-US/legal/license-field/#_rust_packages That would probably benefit from being expanded since it impacts more than just the Rust ecosystem. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ legal mailing list -- legal@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to legal-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
