Add setting to not install packages

If you are installing Salt via git/pip, the formula will try to overwrite your
install with packaged versions. This setting makes it possible to avoid that.

Stop using clean: True on /etc/salt/{minion,master}.d

Add note explaining what clean_config_d_dir does and why you shouldn't set it
to True.

New versions of Salt put config files in /etc/salt/{minion,master}.d. We don't
want to erase them by using a clean: True on the file.recurse. This is a
backward incompatible change, but it's necessary to avoid deleting Salt config
files.

Resolves #104

Don't overwrite salt variable

Using a variable named salt is a bad idea when salt already has a variable
named salt.

Added salt-api support

fix suse os_family

create config option for mine_interval

add mine_get function to master config

don't try to load pkgrepo on non-Debian distros

fixes #83 by wrapping contents of pkgrepo/init.sls in an {% if %}.

Change-Id: I8260fdf5cf802c0b28197516da374add6c3002a2

Fix #39 multi master support to minion

This will fix #39

And it will be backwards compatible with the current pillar configuration.

added rest_tornado to _defaults.conf

see pillar.example for configuration

Updated map.jinja for archlinux package convention

saltify provider should set correct master

This is necessary for the correct settings on the minions when saltifying new hosts

Revert "Add mine_functions to master config template"

Add mine_functions to master config template

updated the map style without the base='default' parameter

fix salt-ssh on Arch and Opensuse

Fix: pkgs is undefined

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.