Add ruby-1.9.3-p484.tar.bz2
ruby-2.0.0-p353.tar.bz2
Add crossfader_ruby_193p484.yaml config
Add crossfader_ruby_200p353.yaml config
Fix ruby version paths for 1.9.3-p484 and 2.0.0-p353

Without this patch the new builds of Ruby are not installing into the
correct locations because the configuration file does not specify the
correct version of the MRI version being built.  This patch addresses
the problem by updating the ruby version to the correct version.
Add crossfader config for Ruby 2.1.0
Install gem list into global gemset

Without this patch each ruby version does not include a default set of
gems.  This is a problem because each ruby version crossfader manages
should ideally include at least bundler.  This patch addresses the
problem by loading a special YAML file located at
config/crossfader_ruby_210_gems.yaml

If the YAML file does not exist then a default global gemset of bundler
is automatically installed for each Ruby version.
Make ruby gemset directories admin writable

Without this patch end users of crossfader cannot install gems without
dropping to root access levels.  This is a problem because sudo resets
the environment which makes usability more difficult.

This patch fixes the problem by packaging crossfader in a manner that
uses recommended permissions for nearly everything except the gemset
directory which is root:admin with 775 unix permissions.
Add version identifier to /opt/crossfader/version.txt

Without this patch there is no version identifier for the installed
version of the full crossfader package.  This is a problem because the
crossfader executable command returns the gem version of crossfader, not
the actual build version.  We need to store and write the build version
in the package in order to display it to the user.

This patch addresses the problem by writing
/opt/crossfader/version.txt when building and before packaging
the crossfader runtime environment itself.  This file is managed by a
small, special package with the same version as the single file written.
Display build version from `crossfader --version`

Without this patch the end user doesn't have an way to easily check
which version of crossfader is currently installed.  When we say
"crossfader version" we generally mean the build version, which is all
of the components in the main distribution package.  This patch augments
the crossfader gem version with an additional build version read from
/opt/crossfader/version.txt
Set CROSSFADER_RUBY during shellinit

Without this patch the CROSSFADER_RUBY environment variable is not set
when initializing the shell environment for crossfader.  This makes it
difficult to hand off the currently initialized environment to a sudo
initialized environment with something like `sudo crossfader
--ruby=$CROSSFADER_RUBY --gemset=$CROSSFADER_GEMSET`.

This patch addresses the problem by setting CROSSFADER_RUBY just like
CROSSFADER_GEMSET is defined during shell initialization.

In addition this patch uses XFADE_PATH_ORIG if it's present in the
enviornment.  This has the behavior of using the original PATH when
constructing a new PATH from a nested invocation of crossfader.
Fix crosfader --version output

Without this patch there is a trailing newline while reading the
crossfader build version file.  This patch addresses the problem by
reading only the first line of the file and making sure trailing
whitespace is chomped off.
Add openssl-1.0.0l
Add openssl-1.0.1f
Add Ruby build for /opt/operations/bin/ruby

Without this patch the Operations team doesn't have a Ruby interpreter
to use for the purpose of running Puppet to manage Mac OS X
workstations.  This is a problem because the Ops team wants to help
improve the overall experience of supporting other employees in their
efforts.  As part of this improvement they'd like to use Puppet to
automate the configuration of laptops.

This patch addresses the problem by providing a dedicated Ruby as part
of crossfader.  The Ops team will have /opt/operations/bin/ruby for
their own needs.

This build requires the following setup phase in the Jenkins job to
build correctly.  This behavior should probably be moved to a `rake
crossfader:setup` task.

    sudo rm -rf /opt/operations
    sudo mkdir /opt/operations
    sudo chown $USER:0 /opt/operations
    sudo chmod 755 /opt/operations

Paired With: Matt Kirby <kirby@puppetlabs.com>
Merge branch 'operations' into crossfader

* operations:
  Add Ruby build for /opt/operations/bin/ruby
  Add openssl-1.0.1f
  Add openssl-1.0.0l
Fix missing crossfader ruby-1.9.3-p484 version

Without this patch there is no 1.9.3-p484 version packaged for
crossfader.  This is a problem because we need this version to validate
against Puppet Enterprise.

The reason this version disappeared is because the ruby version for the
operations team in /opt/operations shares the same package identifier as
the version for crossfader.

This patch addresses the problem by creating a unique package identifier
string for the operations version.
Update to OpenSSL 1.0.0l to address bad ecpoint error.

Without this patch we're getting OpenSSL errors which return "bad
ecpoint"  This patch attempts to address the problem by updating to
OpenSSL 1.0.0l
Add bash_profile example to readme
Merge branch 'libbymo-crossfader' into crossfader

Closes 3

* libbymo-crossfader:
  Add bash_profile example to readme