community.general.portage: add autounmask-backtrack option

[samuliy]

Summary

The module has option for backtrack, but not for autounmask-backtrack.

   --autounmask-backtrack < y | n >
          Allow backtracking after autounmask has detected that configuration changes are necessary. This option is not recommended, since it can cause a large amount of time to be  wasted  by
          backtracking calculations, even though there is no guarantee that it will produce a solution. This option is disabled by default.

Although the option is not recommended due to it possibly making emerge take longer, it makes sense in the case of automated emerge via Ansible, as it may make the emerge more likely to succeed in certain cases where backtracking is required, thus reducing the need for manual remediation.

Issue Type

Feature Idea

Component Name

portage

Additional Information

    - name: Emerge world
      community.general.portage:
        backtrack: 30
        autounmask_backtrack: true
        package: "@world"
        # ... rest of the options

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibullbot]

Files identified in the description:

• plugins/modules/portage.py

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @Tatsh @wltjr
click here for bot help