On Sat, Feb 18, 2012 at 6:18 PM, Mark Knecht <markkne...@gmail.com> wrote: > In a current thread started by Meino where he is having trouble > emerging hydrogen he reported the following quoted data to Neil. I > don't believe Neil has responded yet but Meino's data brought me back > to a question I've meant to ask for a while so I'll take this > opportunity. > > From Meino: > > <QUOTE> > With > > eselect python list > > I get > > Available Python interpreters: > [1] python2.6 > [2] python2.7 > [3] python3.1 > [4] python3.2 * > </QUOTE> > > which shows python3.2 as the system wide default. > > It's been my understanding ever since we first emerged any > python-3.x version that we were not supposed to set any version of > python3 as the system wide default. On all of my systems I have > something like this: > > c2stable ~ # eselect python list > Available Python interpreters: > [1] python2.7 * > [2] python3.2 > c2stable ~ # eselect python list --python2 > Available Python 2 interpreters: > [1] python2.7 * > c2stable ~ # eselect python list --python3 > Available Python 3 interpreters: > [1] python3.2 * > c2stable ~ # > > Now, like Paul Hartman I didn't have any trouble building and > running Hydrogen as a Jack client. It works just fine for me. However > no one else seemed to have picked up on Meino's configuration which > makes me wonder if I missed the memo to make the 3.x version of the > system wide default. > > What is the current best practice in this area? > > Cheers, > Mark >
I still have 2.7 set as default, but even after changing it to 3.2 that package still builds for me (and still shows linux2 not linux3 when it is emerging). The only overlays I use are nx and vmware.
