On 09/18/2017 08:03 PM, Aaron W. Swenson wrote: > On 2017-09-18 15:09, Paul Varner wrote: >> 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 >
We shouldn't be telling people to use --unmerge unless it is a last resort. The preferred way to remove something is with --depclean <package> so they get in good habits and do not break their system. I know this case is a leaf package, so the --deselect and matching blocker should be good enough IMO. Brian
signature.asc
Description: OpenPGP digital signature
