| 1 |
Mark Knecht wrote: |
| 2 |
|
| 3 |
> Dale, |
| 4 |
> I'll try to make it clearer: |
| 5 |
> |
| 6 |
> The command "eselect python set #" sets the system python profile. |
| 7 |
> This command allows you to choose any python currently on your system. |
| 8 |
> You should only choose a python2 setting at this time. |
| 9 |
> |
| 10 |
> The commands: |
| 11 |
> eselect python list --python2 |
| 12 |
> eselect python set --python2 # |
| 13 |
> |
| 14 |
> only deal with python2 |
| 15 |
> |
| 16 |
> The command |
| 17 |
> eselect python list --python3 |
| 18 |
> eselect python set --python3 # |
| 19 |
> |
| 20 |
> only deal with python3 |
| 21 |
> |
| 22 |
> All three of those profiles (python, python2 & python3) are distinct |
| 23 |
> entities. They are different and can each be set any way you want. I |
| 24 |
> was only clarifying that before you removed python3.1 that you choose |
| 25 |
> python3.2 for your python3 profile. |
| 26 |
> |
| 27 |
> Clearer? |
| 28 |
> |
| 29 |
> HTH, |
| 30 |
> Mark |
| 31 |
> |
| 32 |
> |
| 33 |
|
| 34 |
|
| 35 |
I see the difference now. I already ran --depclean and portage still |
| 36 |
works. I'll run python-updater again tho. I didn't know eselect |
| 37 |
treated them separately like that. Learn something every day. |
| 38 |
|
| 39 |
Now to remember that. :/ |
| 40 |
|
| 41 |
Dale |
| 42 |
|
| 43 |
:-) :-) |
| 44 |
|
| 45 |
-- |
| 46 |
I am only responsible for what I said ... Not for what you understood or |
| 47 |
how you interpreted my words! |
| 48 |
|
| 49 |
Miss the compile output? Hint: |
| 50 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |
Archives