Squashed commit of the following:

commit 7ddb9361dbfdd0102c66df99e129ee89ea60361e
Author: Ethan Rowe <ethan@the-rowes.com>
Date:   Thu Aug 22 09:46:37 2013 -0400

    hadupils_script :delete and default_action :create

commit 61d37bd9eeb4043b254653d7a904e8ea7703abcc
Author: Ethan Rowe <ethan@the-rowes.com>
Date:   Thu Aug 22 09:27:22 2013 -0400

    hadupils_script resource

    The hadupils_script resource will, given a path as its name,
    lay down a wrapper bash script at that path, executable by default,
    which simply wraps a call to the hadupils entry point.

    So:
        hadupils_script '/home/foo/bin/hive' do
          action :create
          command hive
          owner foo
        end

    This would create an executable script at /home/foo/bin/hive,
    which under the hood simply calls "hadupils hive $@".

    If :command isn't specified it'll take the basename of the path
    by default.  So in the above example, we could have left out the
    "command hive" line, and gotten the same result.

commit b068e55ba66ad372efeac35f9dcf4ddc5d594086
Author: Ethan Rowe <ethan@the-rowes.com>
Date:   Wed Aug 21 13:31:48 2013 -0400

    hadupils::default and hadupils::install recipes

    Basic stuff:
    - hadupils::default includes hadupils::install and that's it.
    - hadupils::install can install the hadupils gem to both system
      ruby (gem_package) and chef ruby (chef_gem) based on attributes.
    - hadupils::install defaults to install with gem_package but not
      with chef_gem.

commit 922187fda7745852a448173ed4e5902b4c9cd328
Author: Ethan Rowe <ethan@the-rowes.com>
Date:   Wed Aug 21 12:05:01 2013 -0400

    Initial hadupils cookbook layout with empty spec

    TO-DO:
    * Actually implement something meaningful
    * Flesh out attributes definitions and docs in README.md