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.
"brew audit <formula>" will check the given formula for a couple of
known issues:
* Is an explicit mirror being used for a SourceForge download path?
* Is the commented-out cmake support present?
The previous code works fine on ruby 1.8.x, but under 1.9 trying
find on a non-existent folder gives:
==> No such file or directory
/usr/local/Cellar/ruby/1.9.1-p378/lib/ruby/1.9.1/find.rb:38:in `block in find'
FixesHomebrew/homebrew#1633
The TeX-live 2008 formula was out of date (there's a 2009), buggy,
and doesn't build 64-bit.
The MacTeX package works and is supported, with a 2010 version in the works.
Let's recommend that instead.
FixesHomebrew/homebrew#1087
If a package contains a folder that has the same name as one of our
expected meta files, skip trying to install that folder.
(Otherwise we install an empty folder and can get odd permission errors
when trying to summarize after install.)
The code to try to move man into share didn't seem to be working, since
the code that warns if a top-level man was found was firing off.
Removing this apparently dead code.
Different llvm binaries were used to check build numbers and to compile with.
Normalize this, and normalize the variable name used to hold the xcode location.
(Calling it "prefix" is confusing, since there are already concepts in Homebrew
called "prefx".)
Replaced ENV.gcc_4_2 + comments with calls to "fails_with_llvm",
to specifically message to the user when a formula is known or suspected
to not build with LLVM. If the user specifies "--use-llvm", the message
will be displayed, but compilation will be tried anyway.
Since using LLVM is now an advanced/hidden feature instead of the
default on 10.6, we'll let the user try anyway (and submit patches
if things are now working.)
