highlight 3.12

Closes #18106.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
ruby 2.0.0-p0

Closes #18054.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
lftp 4.4.4

Closes #18117.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
libgpg-error 1.11
ruby-build 20130227

Closes #18122.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
ruby: use superenv

env :std was added to this formula without a comment as to why it is
needed, and there appears to be nothing on the issue tracker. Having
used a superenv-built ruby without issue for a few days I am assuming it
was a mistake.

If it causes problems we can either fix them or re-add env :std with
appropriate documentation.
groonga 3.0.1

Closes #18125.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
gnutls 3.1.9

Closes #18126.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
libsoup: add depends_on pkg-config

also disable TLS check, since we provide gnutls

Fixes #18124.
Closes #18127.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
pixie: add required X11 dependency.

see https://gist.github.com/fish2000/5042119

Closes #18103.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
jpeg-turbo: add libjpeg-turbo alias.

References #18113.
mysql: update homepage

Closes #18134.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
bsdconv 9.1

Closes #18129.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
MeCab 0.996

Closes #18130.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
Grails 2.2.1

Closes #18144.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
opam 0.9.4

Closes #18138.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
libgee: depends on pkg-config

Closes #18128.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
Exclude all located superenv paths.

The previous fix only looked at the current Homebrew but we should
discard hits from other installations of Homebrew too.
imagemagick: fix option name
imagemagick: remove X11.installed? conditionals

Unfortunately this won't work as was probably intended; in order for X11
paths to be injected into the build, an X11 dependency has to be active.
It's not enough for it to simply be installed.

It's possible for things to accidentally find X11 under stdenv, but
superenv actually removes X11 paths unless they are explicitly
requested.