Comment 3 for bug 1492186

Some quality issues that I think we should consider in this MIR:

It is a userspace library but upstream does not yet comply with ecosystem best practices for shipping a shared library with respect to FHS paths. It is required to use upstream's build system or do fairly hacky things with cpp and ld flags for an application that uses DPDK to build. I described this to upstream in http://dpdk.org/ml/archives/dev/2015-September/023180.html and they seem receptive to patches to fix this, but this still needs doing. The dpdk-dev binary package (as opposed to libdpdk-dev) shouldn't need to exist. Fixing this will likely require API and ABI bumps upstream. How does this fit with MIR requirements in respect to maintainability of the packaging?