On Sat, Oct 26, 2013 at 09:30:57PM -0400, Mike Gilbert wrote
> The (non-)relationship between eselect python and PYTHON_TARGETS is
> something that would be nice to resolve, but I don't know how to do
> it. PYTHON_SINGLE_TARGET will probably cause problems if/when packages
> start supporting python3 only.
What I find interesting/annoying is that my make.conf has to have 3
lines...
PYTHON_SINGLE_TARGET="python2_7"
PYTHON_TARGETS="python2_7"
USE_PYTHON="2.7"
...as if it didn't hear me the first time. How difficult would it be to
set up an eclass to tell portage that...
if PYTHON_SINGLE_TARGET="pythonX_Y"
PYTHON_TARGETS defaults to "${PYTHON_SINGLE_TARGET}"
USE_PYTHON defaults to "${PYTHON_SINGLE_TARGET/_/.}"
Over-ride the default if explicitly listed. Out of sheer curiousity,
what circumstances are there where ordinary users would need differing
values for these 3 items?
--
Walter Dnes <waltd...@waltdnes.org>
I don't run "desktop environments"; I run useful applications
