The upstream used naming for python-config is 'pythonX.Y-config'. Please fix your package to use that rather than relying on Gentoo-specific 'python-config-X.Y'. This can be often fixed by removing some patch, sed or configure override.
A modern note: if you're using python-r1, python-single-r1 or python-any-r1, it's not necessary to use 'python-config-X.Y' or 'pythonX.Y-config' anymore. The eclass puts a local symlink to proper 'python-config' variant in $PATH, so the build system can just take 'python-config' and it will get the version desired. If the build system in question respects PYTHON and looks for appropriate pythonX.Y-config itself, great! If it doesn't, there's no need to hack it in. Just let it use python-config and the eclass will do the rest.
Hi Michal, this will soon be done in the 2.0 ebuild bump, we'll update this bug pretty soon.
It's covered in this new bump, cheers mate. +*uwsgi-2.0 (16 Jan 2014) + + 16 Jan 2014; Ultrabug <ultrabug@gentoo.org> -uwsgi-1.0.2.1.ebuild, + -uwsgi-1.2.6.ebuild, -uwsgi-1.9.6.ebuild, +uwsgi-2.0.ebuild, + -files/1.2.6-fixed-typecasting.patch, -files/uwsgi-1.0.2.1-no-werror.patch, + +files/gentoo.buildconf, -files/uwsgi.confd, -files/uwsgi.initd, + metadata.xml: + version bump introducing UWSGI_PLUGINS USE_EXPAND with help of @dev-zero fix + #497534 #497364 #488398 #484366 #469098 #469536, drop obsolete versions, + cleanup +
