https://bugzilla.redhat.com/show_bug.cgi?id=2450007



--- Comment #23 from Jonathan Steffan <[email protected]> ---
(In reply to Tom.Rix from comment #22)
> > 
> >   Symlink chain resolution (pkg/lookup/symlinks/symlink.go): Once a library
> > path is found, the full
> >   symlink chain is walked (e.g., libcuda.so → libcuda.so.1 →
> > libcuda.so.550.1.0) and all aliases are
> >   collected — so containers get every soname variant.
> > 
> 
> cuda is of course not open source.
> What are the legal issues for this method ?
> I am hoping you can point to a past ruling saying it is ok.

Dynamically linking is the licensing demarcation point. Everything shipped in
this package is licensed with an approved license and should be fine for
Fedora. If the relevant DSOs are available in the probed locations, they are
exposed inside the container. If not, nothing happens and the CDI configuration
is unable to be assembled.


-- 
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=2450007

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202450007%23c23

-- 
_______________________________________________
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://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to