| 1 |
On Fri, Sep 2, 2011 at 8:59 AM, James <wireless@×××××××××××.com> wrote: |
| 2 |
> James <wireless <at> tampabay.rr.com> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
>> It is time to remove |
| 6 |
>> dev-lang/python-2.6.6-r2 |
| 7 |
> |
| 8 |
> emerge --depclean -pv =dev-lang/python-2.6.6-r2 |
| 9 |
> |
| 10 |
>>>> Calculating removal order... |
| 11 |
> |
| 12 |
>>>> These are the packages that would be unmerged: |
| 13 |
> |
| 14 |
> dev-lang/python |
| 15 |
> selected: 2.6.6-r2 |
| 16 |
> protected: none |
| 17 |
> omitted: 2.7.1-r1 3.1.3-r1 |
| 18 |
> |
| 19 |
> All selected packages: dev-lang/python-2.6.6-r2 |
| 20 |
> Packages installed: 1289 |
| 21 |
> Packages in world: 101 |
| 22 |
> Packages in system: 45 |
| 23 |
> Required packages: 1287 |
| 24 |
> Number to remove: 1 |
| 25 |
> |
| 26 |
> |
| 27 |
> CAN I TRUST this syntax to test for packages to remove? |
| 28 |
> |
| 29 |
> |
| 30 |
> James |
| 31 |
> |
| 32 |
|
| 33 |
I believe you can trust it, but why use --depclean instead of just -C? |
| 34 |
|
| 35 |
Prior to doing anything please ensure that you have eselect python |
| 36 |
setup correctly for a python-2.7 package that's on the machine. |
| 37 |
|
| 38 |
HTH, |
| 39 |
Mark |
Archives