In certain situations, a user may want to allow emerge --autounmask to operate without any human interaction. For example, this sort of behavior can be very useful in a continuous integration setting, where the emerge invocation might be inside of a container that is later discarded (so there is no threat of negative consequences). It would be very handy to have an emerge --autounmask-continue option to trigger this sort of behavior.
I've started working on a patch here: https://github.com/zmedico/portage/tree/bug_582624
Patch posted for review: https://archives.gentoo.org/gentoo-portage-dev/message/9e8540299ee422a56a316bb08cc339ad https://github.com/gentoo/portage/pull/32
This is in the master branch: https://gitweb.gentoo.org/proj/portage.git/commit/?id=e2d88ef3ff5958571ef2da5f69e8756522390f0f
Would it be possible to combine that with some option similar to -a to make emerge more interactive? "Would you like to write these USE-changes and continue? [Yes/No] _" That would be great.
(In reply to Simon from comment #4) > Would it be possible to combine that with some option similar to -a to make > emerge more interactive? > "Would you like to write these USE-changes and continue? [Yes/No] _" > > That would be great. Yes, it does that already, using the same "Would you like to add these changes to your config files?" prompt as before.
Fixed in portage-2.3.3.
*** Bug 299631 has been marked as a duplicate of this bug. ***
