----- Original Message -----
From: "Nicolas Mailhot"
<nicolas.mailhot(a)laposte.net>
To: golang(a)lists.fedoraproject.org
Sent: Monday, March 5, 2018 4:45:31 PM
Subject: Re: vendored dep licenses to include (or skip) in binary rpms
Le lundi 05 mars 2018 à 10:07 -0500, Lokesh Mandvekar a écrit :
> When you ship a Go binary like cri-o, do you need to include the
> licenses of all vendored dependencies at %license? Or does it suffice
> to specify just the license file of the main package itself?
.
.
.
3. it is *way* simpler with dynamic linking where all the objects
are
nicely separated, in different packages, with separate documentation,
and legal analysis can be made at the time you assemble the packages,
not at the time you ship them. Volunteers willing to convert Fedora
packages to dynamic linking are welcome.
Nicolas,
I would much appreciate if you could help me to convert Fedora to dynamic linking in
regard to the the Go packaging. May I count you in?
JC
> 4. if you publish a Go project: don't vendor, use stable releases of
> other components, and if you do vendor don't include the vendored files
> in you git repo, just the vendor config file.
>
> But do ask spot or fedoral-legal when in doubt.
>
> Regards,
>
> --
> Nicolas Mailhot
> _______________________________________________
> golang mailing list -- golang(a)lists.fedoraproject.org
> To unsubscribe send an email to golang-leave(a)lists.fedoraproject.org
>