1 |
On 2017-09-18 15:09, Paul Varner wrote: |
2 |
> Please provide any feedback on the upcoming deprecation and removal of |
3 |
> app-portage/gentoolkit-dev with the upcoming stabilization of |
4 |
> app-portage/gentoolkit-0.4.0 (Bug 627350) |
5 |
> |
6 |
> Regards, |
7 |
> Paul |
8 |
|
9 |
> Title: app-portage/gentoolkit-dev deprecation/removal |
10 |
> Author: Paul Varner <fuzzyray@g.o> |
11 |
> Posted: 2017-09-19 |
12 |
> Revision: 1 |
13 |
> News-Item-Format: 2.0 |
14 |
> Display-If-Installed: app-portage/gentoolkit-dev |
15 |
> |
16 |
> The app-portage/gentoolkit-dev package has been deprecated and the ebump, |
17 |
> ekeyword and imlate have been moved to the app-portage/gentoolkit-0.4.0 |
18 |
> package. With the upcoming marking of >=app-portage/gentoolkit-0.4.0 stable, |
19 |
> users will need to take action since gentoolkit-dev and those versions of |
20 |
> gentoolkit block each other. |
21 |
> |
22 |
> In order to upgrade to the new version of gentoolkit, you will need to resolve |
23 |
> the blocks. In many cases, removing app-portage/gentoolkit-dev from the world |
24 |
> set will allow Portage to automatically resolve the blockers and remove |
25 |
> gentoolkit-dev. You can remove it from world using the following command. |
26 |
> |
27 |
> emerge --deselect app-portage/gentoolkit-dev |
28 |
> |
29 |
> If that fails to work, then unmerge the gentoolkit-dev package with |
30 |
> |
31 |
> emerge --unmerge app-portage/gentoolkit-dev |
32 |
> |
33 |
|
34 |
Why not just instruct users to unmerge rather than attempt something |
35 |
that may or may not work as a first step? |
36 |
|
37 |
The instructions would the be simplified to: |
38 |
In order to upgrade to the new version of app-portage/gentoolkit, first |
39 |
unmerge app-portage/gentoolkit-dev then emerge app-portage/gentoolkit: |
40 |
|
41 |
# emerge --unmerge app-portage/gentoolkit-dev |
42 |
# emerge --ask app-portage/gentoolkit |