aboutsummaryrefslogtreecommitdiffstats
path: root/Library/Homebrew/cmd/--config.rb
AgeCommit message (Collapse)Author
2014-04-30--config -> configAdam Vandenberg
2013-11-01Remove "-c1" one-line configJack Nagel
This is broken and nobody noticed, so remove it. Closes Homebrew/homebrew#23878.
2013-10-24config: omit llvm-gcc if it's not installedJack Nagel
2013-10-22Avoid comparing Xcode.version to floatsJack Nagel
2013-10-04config: squelch stderr when invoking gitJack Nagel
2013-08-26Prefer interpolation to concatenationJack Nagel
2013-04-06Replace literal paths to ruby with RUBY_PATHJack Nagel
2013-03-23Hardware: separate out CPU values into CPU moduleMisty De Meo
* CPU functions now exist in Hardware::CPU * Added compatibility functions in compat/hardware_compat.rb * Names are less specific to Mac hardware, e.g. CPU.family instead of Hardware.intel_family * Hardware::CPU.family works for both Intel and PowerPC * New helper methods on CPU, like .sse4? and .altivec? Signed-off-by: Misty De Meo <mistydemeo@gmail.com>
2013-01-17Doctor check for originSimon Sigurdhsson
Added checks on doctor.rb for: * Missing git origin * git origin not pointing at mxcl/homebrew Tests use `git config --get remote.origin.url`. Also added printout of origin to --config.rb. Fixes Homebrew/homebrew#14399. Closes Homebrew/homebrew#17117. Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-12-17Better reporting for MacPorts/Fink installationsJack Nagel
closes Homebrew/homebrew#15853.
2012-12-12Improve Xcode and CLT config reportingJack Nagel
We support three configurations: Xcode-only, CLT-only, and Xcode with CLT. Our configuration output should correctly reflect this. While MacOS::Xcode.version has to continue to return a guess if Xcode is not installed in order to maintain backwards compatibility, this is an implementation detail that we don't need to expose to the user. And it makes `brew --config` output confusing. So let's only print the "Xcode" line when an actual Xcode installation is present. This makes it easy to quickly figure out which of the three possible configurations the user is running. Addresses Homebrew/homebrew#14941, more or less.
2012-09-28Safer way to redirect puts to a fileMax Howell
2012-09-28Only handle build-errors when it's a build-errorMax Howell
Refs Homebrew/homebrew#15164.
2012-09-14Restore X11 description to --config outputJack Nagel
Oops. Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-09-11Remove dead codeJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-09-05Remove fink/macports from verbose --config if they are not present.Adam Vandenberg
2012-09-05Improve `brew --config` responsivenessJack Nagel
Rather than build the whole output in a string, print each item as we go. This gives the illusion of improved responsiveness by delaying the expensive method calls until after the faster output. Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-08-31`brew -c1` one line configuration summaryMax Howell
At your option: `brew --config -1`.
2012-08-14--config: remove confusing XQuartz annotationJack Nagel
Apple's X11 is XQuartz, but this can be confusing, and is ultimately unnecessary for debugging purposes. Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-08-06Adjust XQuartz/X11 module naming schemeJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-08-01Move X11 machinery into MacOS::XQuartz namespaceJack Nagel
In order to better support Xcode-only systems, where X11 libs and executables live under /usr/X11 but headers live in the SDK, move the x11_* helper methods into a new module. This allows us to keep some of the CLT/Xcode-only and Apple X11/XQuartz logic hidden from outside code, like ENV.x11. Since Apple's X11 is actually XQuartz, name the module "MacOS::XQuartz".
2012-07-25Split Xcode and CLT methods into separate modulesJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-07-08Restore some things to failed install config dumpJack Nagel
Closes Homebrew/homebrew#11091. Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-07-08Display compiler build numbers in config dumpJack Nagel
But only display them if they are out of sync with the corresponding Xcode version. Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-07-08Always output X11 version and path in config dumpJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-07-01Better describe X11 in brew --configCamillo Lugaresi
2012-06-26config: omit Xcode path for CLT-only systemsJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-06-26Clean up --config outputJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-06-24Core change: XCode only install, with CLT or bothsamueljohn
Allow XCode without the Command Line Tools to work with homebrew, so it's not necessary to register an Apple Dev ID and/or go to the XCode prefs and download the CLT. Yay! Further, this commit allows to use the CLT solely (without the need for XCode). Saves quite some megs. (Some furmulae require xcodebuild) Of course XCode together with the CLT is still fine and has been tested on 10.7 and 10.6 with Xcode 4 and Xcode 3. Only on Lion or above, tell the user about the options, which are - Xcode without CLT - CLT without Xcode - both (ok, it's not directly stated, but implicit) So if no Xcode is found and we are on Lion or above, we don't fail but check for the CLTs now. For older Macs, the old message that Xcode is needed and the installer should be run is still displayed. If the CLT are not found but Xcode is, then we print out about the experimental status of this setup. Closes Homebrew/homebrew#10510. Signed-off-by: Adam Vandenberg <flangy@gmail.com>
2012-06-01Replace /usr/bin/ruby with full Framework pathMisty De Meo
Rationale: some users insist on replacing the /usr/bin/ruby symlink to point to another ruby on their system, which may break homebrew. Use the full Framework path instead, which is less likely to be tampered with. This also reorganizes the brew --config checks to reflect the different path. Fixes Homebrew/homebrew#12009. Closes Homebrew/homebrew#12333. Signed-off-by: Misty De Meo <mistydemeo@gmail.com>
2012-05-13Use 'which' helper method moreJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-03-24Fix typo in --config.rbJack Nagel
Closes Homebrew/homebrew#11183. Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-03-16Concise --config output for build errorsMax Howell
Rationale, lets only pay attention to the output when it matters. Speeding up diagnosis.
2012-02-29Play nice with case-sensitive filesystemsMax Howell
2012-02-27Show real path to x11 in --config outputJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-02-08brew --config: properly handle empty `which` stringssamueljohn
Symptom: If no python/ruby/perl is in your path, then `which x`.chomp returns an empty string and `unless ""` is still true. So, N/A is never displayed. Instead, ruby's Pathname.new("").realpath returns the cwd. (I consider this realpath behavior a ruby bug) Fix: use empty? Closes Homebrew/homebrew#10027. Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-02-02Show which Perl, Python and Ruby are in the path.Adam Vandenberg
2012-01-11Make MacOS.clang_build_version more usefulJack Nagel
Let's choose the first \d{2,} as the build number, as it is the most likely to indicate significant changes, and we need something to use for comparison when selecting compilers. Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2011-12-28config: prettify sha methodJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2011-12-21Clean up --configAdam Vandenberg
2011-11-25brew-config: remove recommended compiler versionsAdam Vandenberg
The recommended compiler versions printed from `brew-config` are out of date and misleading. The recommendation is always "Run the latest version of Xcode available for your platform".
2011-11-25Display clang version in --config outputJack Nagel
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2011-05-18Create method for accessing Xcode version.Mike McQuaid
2011-03-26remove whitespaceAdam Vandenberg
2011-03-12Don't throw if no gcc 4.0 installedMax Howell
2011-03-12Refactor the brew command into one file per commandMax Howell
The code was sucking. To the extent that maintenance was hard. It's a lot easier to work with code that is sensibly split at sensible boundaries. So now it is more like that. But the refactor is minimal. Because we don't want you to have more merge hell than absolutely necessary. If you merge you will need to pay attention to brew.h.rb (as it is deleted) and bin/brew (as command logic is gone). It will be painful, but you will just have to help git out by moving any changes around manually. Note compatibility.rb. It ensures that any function renames or removals don't break anything. We're pretty serious about backwards compatibility. And that's because we encourage you to hack around with the innards. And we couldn't do that if we would then just make stuff disappear behind your back.