Paige Thompson wrote:
>
> I don't think I removed it, just figured out how to change it with
> eselect. Here's what I mean:
>
>
> laptop#eselect python
> Usage: eselect python <action> <options>
>
> Standard actions:
>  help                     Display help text
>  usage                    Display usage information
>  version                  Display version information
>
> Extra actions:
>  list                     List installed Python interpreters
>    --python2                 List installed Python 2 interpreters
>    --python3                 List installed Python 3 interpreters
>  set <target>             Set main active Python interpreter
>    --python2                 Set active Python 2 interpreter without
> setting of main active Python interpreter if it is not set to Python 2
>    --python3                 Set active Python 3 interpreter without
> setting of main active Python interpreter if it is not set to Python 3
>  show                     Show main active Python interpreter
>    --ABI                     Show Python ABI in format of PYTHON_ABI
> variable
>    --python2                 Show active Python 2 interpreter
>    --python3                 Show active Python 3 interpreter
>  update                   Switch to the most recent CPython interpreter
>    --if-unset                Do not override existing implementation
>    --ignore SLOT             Ignore SLOT when setting symlinks
>    --python2                 Set active Python 2 interpreter without
> setting of main active Python interpreter if it is not set to Python 2
>    --python3                 Set active Python 3 interpreter without
> setting of main active Python interpreter if it is not set to Python 3
> laptop#
>
>
> >From this information I wouldn't expect :
>
> laptop#eselect python set python2.7
> laptop#
>
> To have been correct... since it lists --python2 and --python3 below
> "set" in the help but:
>
> laptop#python --version
> Python 2.7.7
> laptop#
>
> It does, and thats pretty much all I needed. No need to unmerge anything
> but the thought did cross my mind and if I were going to I would've made
> a binpkg first.
>
> Thanks,
>
> -Paige
>

You may want to look into the buildpkg option in make.conf.  It builds
them automatically for you as you emerge things.  I've had a close call
or two so I have had that set for many years now.  If you do set that,
remember to use eclean-pkg on occasion if you start using a lot of hard
drive space. 

You also may want to look into eclean-dist too.  ;-)

Dale

:-)  :-) 

Reply via email to