Fixes in apt module doc: typos, examples

Fix empty requirements specifications in modules documentation

no uses get_bin_path for 2nd use of ip tool

-o and -r option don't exist on AIX

Add support for crypted passwords to password lookup

Add an update option to the git module

apt now uses module function to find bin paths

flowdock module returns changed=false on succes

Fix registered variable usage example

fix package mentioned twice in setup.py

update archlinux PKGBUILD for pacman 4.1

Added a helpful example to the ec2_facts doc.

Campfire Notification Module: Typo fixes, tighter error handling, corrected check mode support

jabber module returns changed=false on success

notification modules irc, mqtt now exit with changed=False

Make package version comparison use globbing.

Pip's name key can now accept remote package address.

**Summary**:

There was a bug in the previous commit; pip module would add --use-mirrors options to a source package when state is absent. The bug is resolved in this commit by checking ``not is_package`` in the if branch.

Furthermore, in order to support non-vcs source name like tarballs, we must not add -e option to the arg list. Given this circumstance, this commit have is_tar and is_vcs and the latter is checked to add -e option. Since mirrors do not make sense with vcs or tarball source, this commit will not add --use-mirrors (default to True) as always.

Fix for issue #2916 : for each host promote the host variables as global...

Fix for issue #2916 : for each host promote the host variables as globally scoped variables for the sake of the groups determination

And also be liberal in what ansible-doc accepts as an empty
requirements specification.

While here fix a typo in template module documentation
wrt jinja2 overrides example.

module needs this added to many tool invokations, but his is a start
Signed-off-by: Brian Coca <briancoca+dev@gmail.com>

Added new parameter 'encrypt' with same semantics from that of
vars_prompt. When encryption is requested a random salt will be
generated and stored along the password in the form:
'<password> salt=<salt>'.

Also store passwords with an ending '\n' for easier looking at files
with console tools. File content was being already rstripped so this
is harmless.

This will allow just making sure the repo exists w/out actually making
any chnages to it. Useful if you're going to run a play repeatedly
against a host that might have active development going on in the
repository (think initial bootstrap of a developers system, and
continued playbook runs to work on other projects).

Signed-off-by: Brian Coca <briancoca+dev@gmail.com>

changed lockfile to be opened in write mode

exclusive locks on read)
Signed-off-by: Brian Coca <briancoca+dev@gmail.com>

Signed-off-by: Brian Coca <briancoca+dev@gmail.com>