| 1 |
On Thu, Mar 24, 2011 at 07:28:35PM -0500, Dale wrote: |
| 2 |
> Mark Knecht wrote: |
| 3 |
> > One of my machines just saw a python-2.7 update and the ebuild was |
| 4 |
> > good enough to remind me to run python-updater, but it didn't suggest |
| 5 |
> > that I run eselect python and set the active version to 2.7. |
| 6 |
> > |
| 7 |
> > Should this new version python be selected first as the active python |
| 8 |
> > 2 version and then run python-updater? |
| 9 |
> > |
| 10 |
> > Thanks, |
| 11 |
> > Mark |
| 12 |
> > |
| 13 |
> > |
| 14 |
> |
| 15 |
> And if we should set python to 2.7, should we remove python-2.6? I |
| 16 |
> don't think we want to break something, portage in particular. ;-) |
| 17 |
> |
| 18 |
> Dale |
| 19 |
> |
| 20 |
> :-) :-) |
| 21 |
|
| 22 |
I run emerge -uvND world && emerge --depclean, the python 2.6 was |
| 23 |
auto removed... |
| 24 |
|
| 25 |
I run eselect python and set the active version to 2.7, then running |
| 26 |
python-updater now.. |
Archives