Comment 9 for bug 1814060

dpdk-doc is useful, but mostly is:
a) a collection of the upstream docs as you'd read them on [1] as well
b) an API reference (generated)
c) a collection of usage examples (code)

For (a) and (b) it is not important to be in main.
A main+security system can work just fine without dpdk-doc.
But vice versa I'm concerned about the promises people might have on the code examples being in main. So we should remote them.

They are currently auto-promoted as the -dev packages were that we discussed above.
I'm extending the Extra-Exclude in that regard.

[1]: https://doc.dpdk.org/guides-18.11/rel_notes/release_18_11.html