*** Private as long as still processing FFE and filling in the template ***
[Availability]
The source code is available from: git://dpdk.org/dpdk
General information: http://dpdk.org
[Rationale]
The DPDK library will be a build dependency for openvswitch package (extra variant using DPDK instead of kernel network stack). Potentially there will be more projects doing the same, so this should be part of the endorsed set of packages.
[Security]
[Quality assurance]
[Dependencies]
texlive-fonts-extra is in universe (!)
[Standards compliance]
[Maintenance]
[Background information]
Of the produced binary packages only libdpdk0 and libdpdk-dev would be required to be in main. The texlive-fonts-extra build dependency only is required to process the dpkd-doc binary(-indep) package.
Can we only put the source and both library package into main and by that avoid the dependency issue?
*** Private as long as still processing FFE and filling in the template ***
[Availability] dpdk.org
The source code is available from: git://dpdk.org/dpdk
General information: http://
[Rationale]
The DPDK library will be a build dependency for openvswitch package (extra variant using DPDK instead of kernel network stack). Potentially there will be more projects doing the same, so this should be part of the endorsed set of packages.
[Security]
[Quality assurance]
[Dependencies]
texlive-fonts-extra is in universe (!)
[Standards compliance]
[Maintenance]
[Background information]
Of the produced binary packages only libdpdk0 and libdpdk-dev would be required to be in main. The texlive-fonts-extra build dependency only is required to process the dpkd-doc binary(-indep) package.
Can we only put the source and both library package into main and by that avoid the dependency issue?