No description
e3d608297d
The `--noreplace` argument to `emerge` is generally coupled with `--newuse` or `--changed-use`, and can be used instruct Portage to rebuild a package only if necessary. Simply checking to see if the package is already installed using `equery` is not sufficient to determine if any changes would be made, so that step is skipped when the `noreplace` module argument is specified. The module then falls back to parsing the output from `emerge` to determine if anything changed. In check mode, `emerge` is called with `--pretend`, so it produces different output, and the parsing fails to correctly infer that a change would be made. This commit adds another regular expression to check when running in check mode that matches the pretend output from `emerge`. Signed-off-by: Dustin C. Hatch <dustin@hatch.name> |
||
|---|---|---|
| cloud | ||
| clustering | ||
| commands | ||
| database | ||
| files | ||
| messaging | ||
| monitoring | ||
| network | ||
| notification | ||
| packaging | ||
| source_control | ||
| system | ||
| web_infrastructure | ||
| windows | ||
| .gitignore | ||
| .travis.yml | ||
| __init__.py | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| README.md | ||
| REVIEWERS.md | ||
| VERSION | ||
ansible-modules-extras
This repo contains a subset of ansible-modules with slightly lower use or priority than "core" modules.
All new modules should be submitted here, and have a chance to be promoted to core over time.
Reporting bugs
Take care to submit tickets to the appropriate repo where modules are contained. The repo is mentioned at the bottom of module documentation page at docs.ansible.com.
Testing modules
Ansible module development guide contains the latest info about that.
License
As with Ansible, modules distributed with Ansible are GPLv3 licensed. User generated modules not part of this project can be of any license.
Installation
There should be no need to install this repo separately as it should be included in any Ansible install using the official documented methods.