| 1 |
On 09/18/2017 08:03 PM, Aaron W. Swenson wrote: |
| 2 |
> On 2017-09-18 15:09, Paul Varner wrote: |
| 3 |
>> In order to upgrade to the new version of gentoolkit, you will need to resolve |
| 4 |
>> the blocks. In many cases, removing app-portage/gentoolkit-dev from the world |
| 5 |
>> set will allow Portage to automatically resolve the blockers and remove |
| 6 |
>> gentoolkit-dev. You can remove it from world using the following command. |
| 7 |
>> |
| 8 |
>> emerge --deselect app-portage/gentoolkit-dev |
| 9 |
>> |
| 10 |
>> If that fails to work, then unmerge the gentoolkit-dev package with |
| 11 |
>> |
| 12 |
>> emerge --unmerge app-portage/gentoolkit-dev |
| 13 |
>> |
| 14 |
> |
| 15 |
> Why not just instruct users to unmerge rather than attempt something |
| 16 |
> that may or may not work as a first step? |
| 17 |
> |
| 18 |
> The instructions would the be simplified to: |
| 19 |
> In order to upgrade to the new version of app-portage/gentoolkit, first |
| 20 |
> unmerge app-portage/gentoolkit-dev then emerge app-portage/gentoolkit: |
| 21 |
> |
| 22 |
> # emerge --unmerge app-portage/gentoolkit-dev |
| 23 |
> # emerge --ask app-portage/gentoolkit |
| 24 |
> |
| 25 |
|
| 26 |
We shouldn't be telling people to use --unmerge unless it is a last resort. |
| 27 |
|
| 28 |
The preferred way to remove something is with --depclean <package> so |
| 29 |
they get in good habits and do not break their system. |
| 30 |
|
| 31 |
I know this case is a leaf package, so the --deselect and matching |
| 32 |
blocker should be good enough IMO. |
| 33 |
|
| 34 |
Brian |
Archives