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:
Patch posted for review:
This is in the master branch:
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. ***