build: python site-packages vs. dist-packages

Unlike Fedora and RHEL/CentOS, where python has
/usr/{lib,lib64}/python2.7/site-packages/..., Debian-based
distributions have /usr/lib/python2.7/dist-packages/...

On Debian our python scriptlet to determine this is broken and
incorrectly returns .../site-packages, not .../dist-packages.
Furthermore, the automake/autoconf/pkgconfig bits ahead of our
own scriptlet have already determined the correct location -- all
we need to do is use it.

This change also slightly reworks the BUILD_PYTHON_INC scriptlet
to bring it in line with the style/pattern of the other python
scriptlets provided by autoconf/pkgconfig.

(I do wonder though, why we have two sets of {C,CPP}FLAGS and
LD_FLAGS - PYTHONDEV_CPPFLAGS and BUILD_PYTHON_INC, and
PYTHONDEV_LDFLAGS and BUILD_PYTHON_LIB.

They both have very similar values, but, e.g. BUILD_PYTHON_INC
misses /usr/lib/x86_64-linux-gnu/python2.7 on Debian; even if
that ommission doesn't seem to be hurting us.)

Change-Id: I309a5c781a1d9aee4d7be2867223781bd2ae18fa
BUG: 1389781
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/15755
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Niels de Vos <ndevos@redhat.com>

0 files changed, 0 insertions, 0 deletions