DPDK shared library versioning

[Christian Ehrhardt ]

The upstream DPDK project does not keep sover's on their combined library.
There was some great work to properly version all the sublibraries going into

For now we have to live with the state as (deliver as sover 0) is and all its implications like complex upgrades/updates.
Might be tricky on the first ABI/API bump, but so far we have only few consumers at least.

We have participated on a discussion about in upstream dpdk but that is still open.
And focus is currently elsewhere.
The last suggestion came from RH and was around a linker script that would replace the combined library.
The linker script would then on link time include just the needed (and versioned) sub libraries of DPDK.
We would have a lot of effort packaging that this way, but even if so we will have to wait until upstream really settled on this.

This bug is more about tracking the issue openly.

[Christian Ehrhardt  (paelzer)]

FYI - the linker script solution seems to be refreshed and picked up for 2.3 http://dpdk.org/dev/patchwork/patch/9088/

[Christian Ehrhardt  (paelzer)]

Packaging will change, this will be part of our move to 16.04 and later and should work out fine as far as it looks atm.

[Christian Ehrhardt  (paelzer)]

This was fixed by upstream changing versioning and us adapting to it in Debian and Ubuntu packaging. The recent upload to yakkety fixed that but there is no way to backport this, so no Xenial task needed. It will in some way be available for Xenial via the cloud archive if needed.