heroku-toolbelt 2.34.0

Closes #17240.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
libtermkey: uses libtool

Closes #17241.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
libtermkey 0.16
openrtsp 2013.01.21

Closes #17242.
gource: disable X11.

References #17143.
Fixes #17246.
gource: use X11 if it's installed.

References #17143.
Fixes #17246.
CONTRIBUTING: fix link to Acceptable Formulae.

To match the recent renaming of that wiki article.

Closes #17249.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
CONTRIBUTING: actually fix this time.
shocco: env :userpaths for markdown requirement
Clean up Tab creation
Move option comparison into BuildOptions
Options can be used interchangeably with Strings

We want to be able to use Option objects in place of strings and have
this be transparent. Defining to_str means that methods like
Kernel#system and Kernel#exec will be able to perform an implicit
conversion.
Options can be dumped as JSON
BuildOptions: simplify setting description
BuildOptions: check has_option? for universal and 32-bit
Refactor option handling internals

Currently we handle options in several ways, and it is hard to remember
what code needs an option string ("--foo"), what needs only the name
("foo") and what needs an Option object.

Now that Option objects can act as strings and be converted to JSON, we
can start using them instead of passing around strings between Formula
objects, Tab objects, and ARGV-style arrays.

The Options class is a special collection that can be queried for the
inclusion of options in any form: '--foo', 'foo', or Option.new("foo").
Move BuildOptions to a separate file
Tests for BuildOptions
Tab#with? to mirror BuildOptions#with?

Eventually a common interface could be factored out into a module, but
for now this will suffice.
Formula#recursive_dependencies

This behaves like recursive_deps, but the resulting list consists of
Dependency objects instead of Formula objects. The list maintains the
installable order property of recursive_deps.

While in the area, add some comments clarifying the purpose of related
methods.