On 2017-09-18 15:09, Paul Varner wrote: > Please provide any feedback on the upcoming deprecation and removal of > app-portage/gentoolkit-dev with the upcoming stabilization of > app-portage/gentoolkit-0.4.0 (Bug 627350) > > Regards, > Paul
> Title: app-portage/gentoolkit-dev deprecation/removal > Author: Paul Varner <[email protected]> > Posted: 2017-09-19 > Revision: 1 > News-Item-Format: 2.0 > Display-If-Installed: app-portage/gentoolkit-dev > > The app-portage/gentoolkit-dev package has been deprecated and the ebump, > ekeyword and imlate have been moved to the app-portage/gentoolkit-0.4.0 > package. With the upcoming marking of >=app-portage/gentoolkit-0.4.0 stable, > users will need to take action since gentoolkit-dev and those versions of > gentoolkit block each other. > > In order to upgrade to the new version of gentoolkit, you will need to resolve > the blocks. In many cases, removing app-portage/gentoolkit-dev from the world > set will allow Portage to automatically resolve the blockers and remove > gentoolkit-dev. You can remove it from world using the following command. > > emerge --deselect app-portage/gentoolkit-dev > > If that fails to work, then unmerge the gentoolkit-dev package with > > emerge --unmerge app-portage/gentoolkit-dev > Why not just instruct users to unmerge rather than attempt something that may or may not work as a first step? The instructions would the be simplified to: In order to upgrade to the new version of app-portage/gentoolkit, first unmerge app-portage/gentoolkit-dev then emerge app-portage/gentoolkit: # emerge --unmerge app-portage/gentoolkit-dev # emerge --ask app-portage/gentoolkit
signature.asc
Description: Digital signature
