Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add document describing the goals and plan of p4c software license tracking #5110

Open
wants to merge 16 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add notes to the two sections describing GPL v2 source files ...
... making it very clear that we expect these files not to be used as
part of a P4 compiler executable.

Signed-off-by: Andy Fingerhut <andy.fingerhut@gmail.com>
  • Loading branch information
jafingerhut committed Jan 24, 2025
commit 655ab710d8049177574fc7329623fd830bc11482
11 changes: 11 additions & 0 deletions license-details/README.md
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add reference to this file into the LINCENSE file, below the actual license.

Original file line number Diff line number Diff line change
@@ -65,6 +65,9 @@ allowed.

## Python source files that import the Scapy package

Note: All of the source files in this section are _only_ for running
tests, and are _not_ part of a compiled `p4c` executable.

The Python library Scapy is released under the GNU General Public
License v2.0 [2].

@@ -102,6 +105,14 @@ companies will want to add proprietary extensions to.

## C files intended to be compiled and executed in the Linux kernel, e.g. EBPF

Note: When analyzing the source files in this section more carefully,
we will take special care to ensure that they are not files used to
build a P4 compiler executable, and update this note when that task is
complete with our findings.

All of the source files in this section are _only_ for running
tests, and are _not_ part of a compiled `p4c` executable.

One or more published P4C back ends produce C source files that are
intended to be compiled and loaded into the kernel via the EBPF
feature, at least [3], [4] and perhaps others.
Loading