Bug 582624 – sys-apps/portage: add emerge --autounmask-continue option to apply autounmask changes and continue

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Zac Medico 2016-05-10 05:13:52 UTC]

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.

[Comment 1 Zac Medico 2016-06-27 09:31:37 UTC]

I've started working on a patch here:

https://github.com/zmedico/portage/tree/bug_582624

[Comment 2 Zac Medico 2016-07-01 07:41:43 UTC]

Patch posted for review:

https://archives.gentoo.org/gentoo-portage-dev/message/9e8540299ee422a56a316bb08cc339ad

https://github.com/gentoo/portage/pull/32

[Comment 3 Zac Medico 2016-07-02 21:06:54 UTC]

This is in the master branch:

https://gitweb.gentoo.org/proj/portage.git/commit/?id=e2d88ef3ff5958571ef2da5f69e8756522390f0f

[Comment 4 Simon 2016-08-25 22:45:54 UTC]

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.

[Comment 5 Zac Medico 2016-08-25 23:31:12 UTC]

(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.

[Comment 6 Zac Medico 2017-02-10 18:47:25 UTC]

Fixed in portage-2.3.3.

[Comment 7 Zac Medico 2020-01-18 00:20:30 UTC]

*** Bug 299631 has been marked as a duplicate of this bug. ***