Update sls files to match name change in map.jinja.

fix #84 with same logic as dnsmasq-formula

Removed package_map lookup

Add support for presence_events setting in master config template

Added map.jinja solution more in line with other formulas,
This also improves issue #30

and pull request #30

updated minion _defaults.conf to version 2014.7

Add saltify provider, map and profile templates

Fix regression for old salt versions and bugfix for event_return_whitelist/event_return_blacklist options

If those options are set in pillar data, the jinja template
salt/files/master.d/_defaults.conf would fail to compile trying to
evaluate non-existing variables.

Replace those variables with the corresponding dictionnary entries.

This is only needed for salt versions older than 2014.7 that do not
define the global "salt" variable in such context.

Most include do not expect salt to be something else than the usual salt
variable giving access to all the salt modules. Instead we use cfg_salt.
And for consistency we rename the master/minion variables to
cfg_master/cfg_minion too.

This commit also provides a more concrete example of a 'host' to
be saltified.  Users can do

    salt-cloud -p make_salty someinstance

or

    salt-cloud -m /etc/salt/cloud.maps.d/foo.conf

Either which way the online docs should really be updated with more
concrete examples.

FIxes for nodegroups/log_granular_levels settings and small cleanups

Add new “salt.formulas” state to manage salt formulas

In Python 3, dict.items() is already an iterator while dict.iteritems() no
longer exits. In Python 2, dict.items() is not an iterator but it works
and the small performance hit doesn't really matter for the salt config
pillar data which is really small.

Otherwise you get an “ValueError: too many values to unpack” exception
when you make use of those entries in your pillar data.

This state downloads formulas from git repositories and ensures
that they are recorded in the file_roots setting.

Updated master config file to 2014.7

Fix link and title in salt.standalone section of README.rst

Add new “salt.pkgrepo” state

This state enables the official saltstack package repository in order to
always benefit from the latest version. This state currently only works on
Debian and Ubuntu, and aims to implement the installation recommendations
of the official documentation:
http://docs.saltstack.com/en/latest/topics/installation/index.html

Add a “salt.standalone” state

Fixed explanations, and improved logic code to client_acl

more improvements in _defaults.conf

better newlines with iterations.

fix spacing with gitfs.

This will make the _defaults.conf file for master and minion
better by removing some empty lines in some code blocks

Updated gitfs jinja, to mirror master file

Added support for salt minion gitfs

Gitfs for the minion is possible with salt 2014.7
Updated config _defaults.conf and pillar with example
Tested it on Archlinux with salt-call --local state.highstate

fix opensuse packaging

added openSUSE support

I don't understand why unnecessary ``-`` were added after and before ``{%-`` and ``-%}``

Test if individual gitfs remote is string

https://github.com/saltstack-formulas/salt-formula/issues/64

Fixes issue where a gitfs remote that has no child options would cause an
error. Also fix up bad yaml in pillar example.

adds `yaml_utf8` option to master config

enables use of jinja < 2.6

Commit 2b51a6f0c3 introduced options for gitfs_remotes in a pillar by using a jinja test to see if a parameter is a mapping (dict etc.). This feature however is only available in jinja 2.6 or newer (see http://jinja.pocoo.org/docs/dev/templates/#mapping).
Although this version of Jinja is available on Ubuntu, other OS / package managers do provide older versions (2.2.1 in RedHat 6).

This change makes use of the "iterable" test which should do the exact same thing.

Reference about this config value: http://docs.saltstack.com/en/latest/ref/configuration/master.html#yaml-utf8
Reference why this might be useful: https://github.com/saltstack/salt/issues/3436#issuecomment-61225863