Re: [vpp-dev] Scapy license in VPP
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
Few quick comments and links.
Turns out GPLv2-or-later is not by itself compatible with Apache ,
we need to use GPLv3 (which is compatible with both).
The questions on dynamic linking are still open   .
We probably need to distinguish several Programs
available from VPP repository.
VPP PAPI (library) is a separate distribution
from VPP test framework.
When a user starts VPP test framework,
linking with VPP PAPI in runtime,
therefore creating a derived work.
GPLv3 would apply to that Program,
but it does not mean we need to mention GPLv3
in VPP PAPI license headers.
This only works because VPP PAPI does not share
any code nor data structures specific to VPP test framework.
Modules which link with Scapy do share data structures,
so the "derived work" nature is apparent already in repo.
From: vpp-dev@... <vpp-dev@...> On Behalf Of
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via lists.fd.io
> Why do you say that vpp_papi need to be dual licensed?
I think e-mail reply would be long,
and I will need to address comments anyway,
so I respond via a Gerrit change .
From: Paul Vinciguerra <pvinci@...>
Why do you say that vpp_papi need to be dual licensed?