SMF 1.0.0 - uses rbac 1.0.0 cookbook syntax

- :redefine action changed to :add_rbac to be more clear
  when adding authorizations to a pre-existing SMF service.
- change rbac calls to comply with version 1.0.0 of
  the rbac cookbook.
Depend on fixed rbac
Add license, contributors, change maintainer
Update readme
Do what thou wilt shall be the whole of the Law
smf provider notifies on update, does not use tmp files

Switching away from writing temp files in favor of writing
checksums to Chef::Config.checksum_path.
Bump version to 1.1.0
Add documentation for :add_rbac
fix :delete action to clean up xml/checksum
Bump version to 1.1.1
Ensure that nokogiri uses system libraries
Remove old copyright stuffs
smf::default installs libxslt with package provider
Add stability attribute to manifest
remove duplicate method contexts

move method_context from each exec command to a
higher level that applies to all commands
Reorder readme
Use FileUtils to create xml directory

`directory` LWRP would register to run later. Rather than
coding around this to force the provider to run in the context
of the SMF provider, switch to FileUtils for code ease.
SMF LWRP triggers import/reload if service does not exist

If the manifest already existed and matched the LWRP attributes,
but the service did not actually exist, it would not get imported.
This could happen if you manually ran `svccfg delete`, then reran chef.
SMF service dependencies can be specified

TBD: validation
Remove dependency on nokogiri, use builder

The builder gem is a pure-ruby XML builder implementation,
so that we do not need to install libxslt or compile
nokogiri.