diff options
| author | Mike McQuaid | 2018-02-23 19:39:19 +0000 |
|---|---|---|
| committer | Mike McQuaid | 2018-02-23 19:52:00 +0000 |
| commit | 190e665bb1db54d452ed9e0bf93c6985bd8dab5f (patch) | |
| tree | d7a1a1c8c4ce9189d786f6f44b814afa28cf4a04 /docs/Bottles.md | |
| parent | d05b8522d5f51db5ca2f75fe322848df9b8ff88b (diff) | |
| download | brew-190e665bb1db54d452ed9e0bf93c6985bd8dab5f.tar.bz2 | |
Revert "docs: use short links."
This reverts commit e63a2ee8de12f0f938f6a95cdb9763dbe0187b4a.
Closes #3832.
Diffstat (limited to 'docs/Bottles.md')
| -rw-r--r-- | docs/Bottles.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Bottles.md b/docs/Bottles.md index b216b2731..426b9e91c 100644 --- a/docs/Bottles.md +++ b/docs/Bottles.md @@ -8,7 +8,7 @@ If a bottle is available and usable it will be downloaded and poured automatical Bottles will not be used if the user requests it (see above), if the formula requests it (with `pour_bottle?`), if any options are specified during installation (bottles are all compiled with default options), if the bottle is not up to date (e.g. lacking a checksum) or if the bottle's `cellar` is not `:any` nor equal to the current `HOMEBREW_CELLAR`. ## Creation -Bottles are created using the [Brew Test Bot](Brew-Test-Bot). This happens mostly when people submit pull requests to Homebrew and the `bottle do` block is updated by maintainers when they `brew pull --bottle` the contents of a pull request. For the Homebrew organisations' taps they are uploaded to and downloaded from [Bintray](https://bintray.com/homebrew). +Bottles are created using the [Brew Test Bot](Brew-Test-Bot.md). This happens mostly when people submit pull requests to Homebrew and the `bottle do` block is updated by maintainers when they `brew pull --bottle` the contents of a pull request. For the Homebrew organisations' taps they are uploaded to and downloaded from [Bintray](https://bintray.com/homebrew). By default, bottles will be built for the oldest CPU supported by the OS/architecture you're building for. (That's Core 2 for 64-bit OSs, Core for 32-bit.) This ensures that bottles are compatible with all computers you might distribute them to. If you *really* want your bottles to be optimized for something else, you can pass the `--bottle-arch=` option to build for another architecture - for example, `brew install foo --bottle-arch=penryn`. Just remember that if you build for a newer architecture some of your users might get binaries they can't run and that would be sad! |