Difference between revisions of "Archived-Deb dpdk"
From fd.io
(→Get Involved) |
|||
| Line 2: | Line 2: | ||
|name=deb_dpdk | |name=deb_dpdk | ||
|shortname=deb_dpdk | |shortname=deb_dpdk | ||
| + | |jiraName=DEBDPDK | ||
|projectLead=Christian Ehrhardt | |projectLead=Christian Ehrhardt | ||
|committers= | |committers= | ||
Revision as of 14:38, 15 June 2016
| deb_dpdk Facts |
|
Project Lead: Christian Ehrhardt
Repository: git clone https://gerrit.fd.io/r/deb_dpdk |
Get Involved
What is this actually?
- Producing .deb packages of DPDK for Ubuntu and other Debian-based systems
- Throw together our collection of backports and other features to create a bigger and better DPDK package for all of us
- Testing .deb packaging of DPDK
- Testing by various different dpdk consumers reflected by the different participating people (openvswitch, vpp, odp, ...)
- Over time maybe useful tools and machinery in support / CI of same
- It essentially is a boiler plate to mature contributions in the face of multiple DPDK (packaging) consumers
- Mid term, once testing and packaging is matured; we intend to feed back generic parts (not release dependent) to the main dpdk.org repository
- That should shrink the delta we have to maintain and is the right place to host it
- The rule of thumb is all in /debian but without /debian/patches
- This might eventually allow cross distribution sharing e.g. of init scripts
- We might discuss or even host Distribution release specific patches e.g. patches on top what got released into Debian sid
- but this will in no way be a dpdk release specific a stable tree
- In fact dpdk.org/Intel are working on creating stable trees currently which is great and would be the preferred things we would like to be based on eventually.
