set ARCHFLAGS to avoid compile issue on OS X 10.9
substrate: update libyaml for vuln
substrate: actually should be libyaml 0.1.6
substrate: work with relative symlinks in path
substrate: new bsdtar for Windows
substrate: always get the latest version of Vagrant
substrate/launcher: use latest version on Windows
substrate: new launcher
substrate/launcher: find only real Vagrant
substrate: fix launcher.exe on Windows
substrate: exec vagrant to eliminate bash launch wrapper

The Bash script that wraps Vagrant is badly behaved and eats certain signals.
Launch Vagrant with `exec` to replace the Bash wrapper and allow signals to be
handled directly by Vagrant.

Consider the following:

$ vagrant rsync-auto &
$ kill -INT $!

`$!` returns the PID of the Bash wrapper script, not the Ruby process running
Vagrant. By default, Bash will ignore interrupts while running a command, so
Bash will swallow the signal generated by `kill -INT $!`, even though Vagrant
would exit had it received the signal.

You don't see this behavior on Ctrl-c, since Ctrl-c sends an interrupt to all
processes in the foreground process group—i.e., both Bash and Ruby.

(kill -TERM $! will successfully terminate the processes, but only after
printing an insuppressible "Terminated: 15" message.)
download verpatch and add version info to bsdtar
Merge pull request #36 from benesch/patch-1

substrate: exec vagrant to eliminate bash launch wrapper
Merge pull request #37 from StefanScherer/fix_vagrant_issue_3674_with_verpatch

download verpatch and add version info to bsdtar
package: disable verpatch stuff for now
Create LICENSE.md
added version 3.1.2.0 to bsdtar.exe/bsdcpio.exe
When running vagrant from cygwin, convert the SSL_CERT_FILE path to a Windows path, Ruby doesn't work with cygwin paths
Merge pull request #44 from g0t4/master

Fix for SSL_CERT_FILE in cygwin
Merge pull request #43 from StefanScherer/versioned_bsdtar_for_vagrant_update_problem_3674

added version info to bsdtar.exe to fix MSI update issues