sys-libs/libsemanage-2.1.9 does not build with python-2.6, as it uses pkg-config to locate python directories, and pkg-config metadata seems to be only available beginning with python-2.7 Reproducible: Always Steps to Reproduce: 1. have python-2.6 selected using eselect python, 2. emerge sys-libs/libsemanage Actual Results: * Building of sys-libs/libsemanage-2.1.9 with CPython 2.6... make -j2 CC=i686-pc-linux-gnu-gcc PYLIBVER=python2.6 PYPREFIX=python-2.6 -- pywrap Package python-2.6 was not found in the pkg-config search path. Perhaps you should add the directory containing `python-2.6.pc' to the PKG_CONFIG_PATH environment variable No package 'python-2.6' found i686-pc-linux-gnu-gcc -march=i686 -O2 -pipe -I../include -I/usr/include -D_GNU_SOURCE -Wno-error -Wno-unused-but-set-variable -Wno-unused-variable -Wno-shadow -Wno-unused-parameter -fPIC -DSHARED -c -o python-2.6semanageswig_wrap.lo semanageswig_wrap.c semanageswig_wrap.c:125:20: fatal error: Python.h: No such file or directory Expected Results: The package should build successfully. The package does build successfully with python-2.7 selected.
Indeed; I'm going to take the easy way out here and mark 2.6 as unsupported for the package (RESTRICT_PYTHON_ABIS). I think we can safely say that /at least/ python 2.7 is available on users systems (and better supported than 2.6) and in the near future I can imagine 2.x being deprecated completely. Fixed in CVS
