| Age | Commit message (Collapse) | Author |
|
|
|
/usr/local is in lots of things unrelated to Homebrew so be more specific and look for opt instead.
|
|
Fixes Homebrew/homebrew#19460.
Closes Homebrew/homebrew#22375.
|
|
Update test to reflect that llvm-gcc should take precedence over
non-Apple GCC.
|
|
llvm-gcc should still get priority over non-Apple GCCs.
Fixes Homebrew/homebrew#22424.
|
|
Closes Homebrew/homebrew#22388.
Closes Homebrew/homebrew#22430.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
Closes Homebrew/homebrew#22339.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
|
|
c.f. Homebrew/homebrew#22386.
|
|
|
|
|
|
|
|
|
|
Still in alpha state.
Handles defaults and merging changes with new versions.
Enable by setting the HOMEBREW_GIT_ETC environment variable.
Closes Homebrew/homebrew#15751.
Closes Homebrew/homebrew#17713.
|
|
|
|
|
|
|
|
* Add "--disable-silent-rules" option to autotools-based configure
options.
- Also add comments to notify user removing unrecognized configure
options.
* Add "-DCMAKE_VERBOSE_MAKEFILE=ON" to cmake-based configure options.
|
|
|
|
Fixes Homebrew/homebrew#22347.
|
|
* Fix problem when install exception got swallow and reinstall thinks it
succeeded.
|
|
|
|
Allow `build.with?` and similar methods to be used during the test
phase. The BuildOptions (`build`) are initialized with the
`Tab.used_options` unless explicitly overwritten on the command line.
So basically `build.with?` works in `def install` and in `test do` as
one would naively expect. (For the test, gramatically it should be
`built.with?` but who cares)
If a formula was installed `--with-python`, now the tests are also
run `--with-python`. This enables us to use the `python do ... end` in
a meaningful manner.
Using `python do ... end` blocks for the tests, because the bot.brew.sh has
system python per default and we need to set the PYTHONPATH for the test.
Potentially to different values for Python 2.x and 3.x.
|
|
|
|
* Aborting during reinstall will now restore the originally installed
keg.
- Change install code to pass on CannotInstallFormulaError exception
to caller so it can be reused in reinstall.
* Add "--force-new-install" flag to force installing a new formula.
Closes Homebrew/homebrew#22190.
Signed-off-by: Samuel John <github@SamuelJohn.de>
|
|
Closes Homebrew/homebrew#21557.
Signed-off-by: Samuel John <github@SamuelJohn.de>
|
|
|
|
|
|
PIL has been removed and users should use pillow either
by `pip install pillo` or `brew install samueljohn/python/pillow`.
|
|
For example `brew search homebrew/science` to get a list of all formulae
from that tap, even if not yet tapped.
`brew search <user>/<repo>/<substr>` or
`brew search <user>/<repo> <substr>` to grep for `<substr>`
inside of the tap `<user>/<repo>`.
|
|
- Show a one liner that will append to
the user's ~/.bash_profile. In 95% this will be
ok and we assume zsh people are smart enough
to know what they have to do.
|
|
Improve robustness of `PYTHONPATH` by first unsetting it (during
`satisfy`) so that the `PythonInstalled` can get the `python.version`
and so forth and then, after that, setting the `PYTHONPATH` to our
`global_site_packages`.
In the `python_helper` we append to the `PYTHONPATH` so if that var has
been set in a formula, it is respected.
Brew audit does no longer complain about setting the
`ENV['PYTHONPATH']`.
|
|
that live in the `libexec` dir of a `Cellar`.
|
|
|
|
If a formula is passed with a relative path, the build process might
try to expand it in the wrong directory, where it doesn't exist.
Fixes Homebrew/homebrew#22266.
|
|
This reverts commit 7db9ef9650a44ef8155bf66efd88703e580057b0.
|
|
|
|
ENV.compiler is called outside setting up the build environment, where
values unsupported for user input might have been specified - for
example, GNU GCC executables.
|
|
|
|
There are now a few possible C++ standard libraries a given build could
be using, with subtle incompatibilities and possibility of breakage
when mixed. This makes sure that the dependency chain was compiled in
a compatible manner.
Fortunately all of the Apple compilers use the same libstdc++, and we
don't yet support building with libc++, so this will primarily only
nag users trying to use GNU gcc who already have software installed
with Apple compilers.
Future TODOs:
* Add general support for building with libc++ (compatibility checking
already handled here)
* Possibly track formulae which actually build C++ bindings, so that
users aren't bothered by spurious nagging re: interpreted languages,
pure-C software, etc.
|
|
There are subtle incompatibilities between Apple's libstdc++ and the
libstdc++ used by the various GNU GCC formulae. In addition, we'll
likely also be supporting libc++ in the future, and that's also
incompatible with the other stdlibs.
Tracking it in the tab lets us make sure that dependencies are all
built against the same stdlib to avoid subtle breakage.
|
|
The parent process doesn't have access to the selected compiler, which
will be important in the next commit.
Fortunately the child process already has a filtered and massaged
ARGV, so it has enough information to build the tab itself.
|
|
This adds support for non-Apple GCC compilers in the fails_with code.
A fails_with block for a non-Apple compiler looks like:
fails_with :gcc => '4.8.1' do
cause 'Foo'
end
Non-Apple compilers don't have build numbers, so compiler failures are
based on version strings instead.
Internally non-Apple compilers can be distinguished because they are
passed around as strings instead of symbols.
In addition, this alters the priority list for compilers, with the
following changes:
* Apple GCC 4.2 and LLVM-GCC swap positions, with GCC now taking
priority. (Maybe LLVM-GCC should just go away.)
* Non-Apple GCC compilers are ranked below GCC 4.2 but above LLVM-GCC
and Apple GCC 4.0.
|
|
|
|
|
|
Warn users and point them to `brew postinstall` (which can provide a
backtrace).
Closes Homebrew/homebrew#21887.
|
|
Runs post-install jobs in case they failed or need rerun for any reason.
|
|
|
|
|
|
|