If you add +unicode to the use flags on an stage3 install, emerge dialog will fail on -libncursesw Reproducible: Always Steps to Reproduce: 1. USE="+unicode" emerge dialog 2. 3. Actual Results: libncursesw failed Expected Results: dialog would recognize the USE flag change and re-emerge ncurses Well I don't know what the right procedure is here, but a new Gentoo user won't understand a thing if it fails on such an error. So the dialog ebuild should have some sort of mechanism to recognize that ncurses has been compiled without unicode and recompile it.
Portage can't do that (so far), you need to use 'emerge --newuse -uD world' after changing USE flags.
