Bring in thor and rspec
Standard rspec options
A minimal rspec configuration
Define an empty init command

Includes specs.
Create a binary for command line invocation
Tell RubyGems about our new executable

And also allow it to autodetect the rest of the important source files.
Clean up gem metadata

We're not supposed to specify the date:
http://rubygems.rubyforge.org/rubygems-update/Gem/Specification.html#method-i-date-3D
Adjust wording to make it clear this is testing the CLI
Make it easier to work with pathnames
Have #init create an empty .gpg-known-keys file

This demonstrates how to have the action do something, and how to have
the specs test the result.
Took care of these two items
Add some spacing to improve readability
gpg-known-keys needs to be a directory, not a file

The public key files will be stored underneath here.
Decide on our stance on gpg1 vs gpg2
Install a placeholder README to the gpg-known-keys directory
Define some more requirements
A fake keyring for running tests

Includes a generated key/identity for test@example.com, and a public
key for scott@westarete.com.
Generate an initial .gpg-recipients file
Ignore backup files that get generated by gnupg