Hello,

Currently, we're using python-wrapper to properly respect EPYTHON
in ebuilds. This is a bit hacky since every call to Python has to go
through wrapper which chooses the same implementation over and over
again.

There was a request to handle 'pkg-config --cflags --libs python'
through eselect-python. Of course, we can't wrap pkg-config like we do
Python (well, we can but...).


The alternate solution is something similar to what vala people do. It
addresses all packages calling 'python', 'python2', 'python3'
or 'pkg-config python' and using any of the -r1 eclasses.

The idea is to create a ${T}/bin and ${T}/pkgconfig directories.
In the former, place 'python' and either 'python2' or 'python3'
symlinks proper to current ${EPYTHON}. In the latter, 'python.pc'
and possibly 'python2.pc' or 'python3.pc'. Add the former to ${PATH},
the latter to ${PKG_CONFIG_PATH}.

In -single-r1 and -any-r1 the directory creation and environment
manipulation would be done in pkg_setup(). In python-r1 it would have
to be done in python_export_best (with separate directory)
and python_foreach_impl.


Does this sound like a good solution? Should I run some tests?

-- 
Best regards,
Michał Górny