Michał Górny posted on Mon, 29 Oct 2012 15:45:01 +0100 as excerpted: > Title: PYTHON_TARGETS deployment
[snip] > Lately, a new Python eclasses were deployed and the way of supporting > multiple Python implementations changes with ebuilds being migrated to > them. While before the implementations being installed were used by > default, the migrated packages will instead use explicit choice based on > PYTHON_TARGETS USE flags. This may require action from some of our > users. That paragraph needs help. Try this: Recently, new python eclasses were deployed. As ebuilds migrate, the way they support multiple python implementations will change. The previous method built support for all installed python implementations. The new method uses the PYTHON_TARGETS USE flags to explicitly name the implementations that support should be built for. > If you are running a modern system with Python 2.7 & 3.2, and you didn't > set USE_PYTHON, then you don't have to do anything. The defaults will > fit you. Fewer changes in this paragraph. Try this: If you are running a modern system with Python 2.7 and 3.2 and you haven't set USE_PYTHON, you don't need to do anything. The defaults will continue to work just as they have. The rest of it looks good to me. Extra points for the specific examples, both of PYTHON_TARGETS and of a suitable command-line to get a list of all possibilities. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
