[picture of I Have No Idea What I'm Doing dog]

https://travis-ci.org/sstephenson/ruby-build/builds/23435342

Filenames in git diff patches are prefixed by default by "a/" (source)
and "b/" destination. Such patches don't work with ruby-builds `--patch`
option since it internally uses `patch -p0`.

Prior workarounds were to use either an intermediate step:

    filterdiff --strip=1

or to generate the patch without the prefix in the first place:

    git diff --no-prefix ...

Now, git diff patches are detected by searching for this pattern:

    diff --git a/...

And `patch -p1` is used by default in such cases to strip the 1st
component of filename paths.

Fixes #521, closes #484

From patch(1):

    -f  or  --force
       Assume that the user knows exactly what he or she is doing, and do  not
       ask any questions.  Skip patches whose headers do not say which file is
       to be patched; patch files even though they have the wrong version  for
       the Prereq: line in the patch; and assume that patches are not reversed
       even if they look like they are.  This option does not suppress commen-
       tary; use -s for that.

Fixes #555

Prefer ggrep for grep invocations that use GNU extensions.

Fixes ruby-build on Solaris 11.1

Adding JRuby 1.7.12

OpenSSL library updated to 1.0.1g

Previous versions of the library contain a vulnerability CVE-2014-0160.

Link to releases in the Readme

Stop maintaining the changelog

All releases information has been migrated to GitHub Releases:
https://github.com/sstephenson/ruby-build/releases

This frees core contributors from having to maintain release notes in version
control, and regular contributors from wondering whether they need to edit
CHANGELOG while submitting a pull request.

Benefits of release notes being outside of version control are that they can be
edited post-release.

Seems like sed 4.1.5 on RHEL 5.3 doesn't support `-E`, and sed on OS X doesn't
support `-r` to activate the extended regexp mode. Best to avoid extended regexp
altogether for compatibility.

Fixes #495

References #433

2.0.0-p451 should use libyaml-0.1.6 too

The `-f` option allows for forcing installation of versions that already
exist in the environment. If that option isn't used, then an interactive
prompt is created which causes problems for non-interactive execution of
the command.

This change adds the `-s/--skip-existing` option to not install versions
that already exist, while still exiting as success.

Closes #543

Update libyaml to 0.1.6

Security fix for CVE-2014-2525

Advisory: http://www.ocert.org/advisories/ocert-2014-003.html

If there already exists a valid tarball in the build location, e.g. as
artefact of a previous install using `--keep`, don't re-download the
file, as there is no need.

References #487

Previously, curl and wget were instructed to try to resume the download
if the destination file already exists. This is supposed to be done via
the "Range" HTTP header, but doesn't work well with CloudFront:

    HTTP server doesn't seem to support byte ranges. Cannot resume.

CloudFront is supposed to support ranges, so I don't know what's going
on here. It might be failing only in case the existing file is a fully
downloaded tarball?

In any case, this disables resuming downloads and resorts to simply
re-downloading the tarball always, overwriting the existing file.

Fixes #487

This reverts commit 6cf348e4. See
https://github.com/sstephenson/ruby-build/issues/526#issuecomment-37889552.

Closes https://github.com/sstephenson/ruby-build/issues/526.

Add Rubinius 2.2.6.

Fixes #517

Better to use -f than -e to check for a user-specified definition file.
With -e, if the user accidentally types the name of a directory (or, far
less likely, a device file) with the same name as the Ruby they're
trying to install, they end up with ruby-build doing absolutely nothing
at best, or an error message that could be pretty confusing at worst.

Closes #514