If set, use "HOMEBREW_EDITOR" when editing a single file, or multiple
files in the same folder.
Note that this setting does not affect `brew edit`, since opening
all of Homebrew at once requires an editor with proper project support.
If the top-level formula being installed has any keg-only
dependencies, the lib/include/bin/pkg-config paths for those
deps will be added twice to the ENV vars.
This doesn't break anything, but does make debug output somewhat longer
than it needs to be.
Tidy this up by calling uniq on deps before iterating.
(The cause of this duplication is related to how top-level formula are
run, to support keeping patches in __END__ blocks.)
FixesHomebrew/homebrew#1110
"brew --env" will set up a build environment and then dump certain ENV
variables (CC, CXX, LD, CFLAGS, CXXFLAGS, MAKEFLAGS).
If any of CC, CXX, LD are symlinks, now also output the target compiler.
(Typically these will be symlinks from eg /usr/bin/cc to /usr/bin/gcc-4.2).
This is a diagnostic command which may be merged into --config, turned
into an external command, or removed if it doesn't turn out to be useful.
This Download Strategy is provided for use with sites that
only provide HTTPS and also have a broken cert.
Try not to need this, as we probably won't accept the forulae
into trunk.
Homebrew will now use the svn binary pointed to by HOMEBREW_SVN if set,
use a Homebrew-installed svn if present, finally falling back to the
system-provided svn binary.
If a formula (mplayer) requires a newer version of Subversion than what
Leopard provides, it can use the "StrictSubversionDownloadStrategy"
download strategy to warn the user.
These changes also fix an issue with forcing exports not working on a
stock Leopard subversion, but letting the user either specify a specific
binary or install Subversion via Homebrew and pick that up instead.
A work-in-progress command, "brew which" will show which versions of formulae
you have installed based on what symlinks exist from HOMEBREW_PREFIX back into
the Cellar.
Thus, if you happen to have symlinks into two different versions of a brew in
the Cellar (typically an error), both of those versions will be listed.
This is a diagnostic command, but some of this code will be the basis for
possible future better handling of multiple-versions-at-once.
While it is useful to be able to see the user's path in bug reports, it is
perhaps slightly too intrusive to post this without the user's permission.
A path can have usernames or other project sensitive information, and several
Homebrew users were editing their bug reports to omit this information.
`brew doctor` will still report on the path issues that we typically care
about, so dropping automatic posting of PATH.
If previous non-Homebrew software was installed to /usr/local with "sudo",
then a pkgconfig folder may have been created with restricted permissions.
This will prevent brews (such as glib) from symlinking their .pc files
correctly.
