If you `brew install erlang` and then control-C during the git clone,
you can leave your cloned repo in an invalid state.
This change does a "git status" on the clone if it exists, and nukes
it if the status is invalid (forcing a clean clone.)
The ImageMagick mirrors like to drop old tarballs, which means that our
formula breaks whenever the version we're using disappears.
So I've switched to using their SVN repo (and added a --HEAD build.)
Caveat: Their SVN repo is only served over https, with a bad cert,
so this brew know has a custom SVN download strategy that auto-accepts
that cert.
If this bothers you, get ImageMagick to fix their cert upstream (or
let us know where a stable tarball mirror lives.)
The update_git_pull_output_with_formulae_changes fixture (which consists
of mocked-up `git pull` output) listed a few files as both updated and
deleted. This caused the test_update_homebrew_with_formulae_changes test to
fail. My guess is that this fixture was mocked-up before formula deletion
handling was introduced, and became broken when it was. This revision just
makes this fixture internally consistent, and allows the associated test to
pass.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
"brew audit" will now warn about commented-out dependencies.
Updated formulae that had these to either take them out or rewrite
the comments around them.
Sphinx currently has a download name 'http://sphinxsearch.com/downloads/sphinx-1.10-beta.tar.gz', which homebrew currently can't correctly identify - with a small change to the regex for 'foobar-4.5.0-beta1' (make that trailing number optional) - it works like a charm.
Signed-off-by: David Höppner <0xffea@gmail.com>
snow_leopard_64? (defined in Hardware) is a short-cut for:
MACOS_VERSION >= 10.6 and Hardware.is_64_bit?
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
Java software tends to come with its own mini file layout including
bin, lib and other folders. The lib folder typically holds jars,
which can conflict between packages if linked into HOMEBREW_PREFIX/lib
and aren't needed to compile other .dylib based software anyway.
The recommendation for Java software is to install to "libexec" and then
symlink or wrap binaries from libexec/bin to bin in the Cellar.