- [ ] Ran `brew update` and retried your prior step?

- [ ] Ran `brew doctor`, fixed as many issues as possible and retried your prior step?

- [ ] If you're seeing permission errors tried running `sudo chown -R $(whoami) $(brew --prefix)`?

_You can erase any parts of this template not applicable to your Issue._

Please replace this line with a brief summary of your issue **AND** if reporting a build issue include the link from:

(where `<formula>` is the name of the formula that failed to build).

**Please note by far the quickest way to get a new feature or formula into Homebrew is to file a [Pull Request](https://github.com/Homebrew/homebrew/blob/master/.github/CONTRIBUTING.md).**

We will consider your request but it may be closed if it's something we're not actively planning to work on.

- [ ] Have you followed the guidelines in our [Contributing](https://github.com/Homebrew/homebrew/blob/master/.github/CONTRIBUTING.md) document?

- [ ] Have you checked to ensure there aren't other open [Pull Requests](https://github.com/Homebrew/homebrew/pulls) for the same update/change?

_You can erase any parts of this template not applicable to your Pull Request._

- [ ] Does your submission pass

`brew audit --strict --online <formula>` (where `<formula>` is the name of the formula you're submitting)?

- [ ] Have you built your formula locally prior to submission with `brew install <formula>`?

- [ ] Have you added an explanation of what your changes do and why you'd like us to include them?

- [ ] Have you written new tests for your core changes, as applicable? [Here's an example](https://github.com/Homebrew/homebrew/pull/49031) if you'd like one.

- [ ] Have you successfully ran `brew tests` with your changes locally?

The Homebrew community is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences great successes and continued growth. When you're working with members of the community, we encourage you to follow these guidelines which help steer our interactions and strive to keep Homebrew a positive, successful, and growing community.

A member of the Homebrew community is:

Members of the community are open to collaboration, whether it's on GitHub, email, IRC or otherwise. We're receptive to constructive comment and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts. We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference.

Members of the community are considerate of their peers - other Homebrew users. We're thoughtful when addressing the efforts of others, keeping in mind that oftentimes their labor was completed simply for the good of the community. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views.

Members of the community are respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts. We're respectful of the volunteer efforts that permeate the Homebrew community. We're respectful of the processes set forth in the community, and we work within them. When we disagree, we are courteous in raising our issues.

Overall, we're good to each other. We contribute to this community not because we have to, but because we want to. If we remember that, these guidelines will come naturally.

The Homebrew community welcomes and encourages participation by everyone. Our community is based on mutual respect, tolerance, and encouragement, and we are working to help each other live up to these principles. We want our community to be more diverse: whoever you are, and whatever your background, we welcome you.

We have created this diversity statement because we believe that a diverse Homebrew community is stronger and more vibrant. A diverse community where people treat each other with respect has more potential contributors and more sources for ideas.

Although we have phrased the formal diversity statement generically to make it all-inclusive, we recognise that there are specific attributes that are used to discriminate against people. In alphabetical order, some of these attributes include (but are not limited to): age, culture, ethnicity, gender identity or expression, national origin, physical or mental difference, politics, race, religion, sex, sexual orientation, socio-economic status, and subculture. We welcome people regardless of the values of these or other attributes.

This code of conduct is heavily based on the [Python Community Code of Conduct](https://www.python.org/psf/codeofconduct/) and the [Python Diversity Statement](https://www.python.org/community/diversity/).

Features, usage and installation instructions are [summarised on the homepage](http://brew.sh).

1. Type `brew search` for a list.

2. Or visit [braumeister.org](http://braumeister.org) to browse packages online.

3. Or use `brew search --desc` to browse packages from the command line.

`brew help`, `man brew` or check [our documentation](https://github.com/Homebrew/homebrew/tree/master/share/doc/homebrew#readme).

First, please run `brew update` and `brew doctor`.

Second, read the [Troubleshooting Checklist](https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Troubleshooting.md#troubleshooting).

**If you don't read these it will take us far longer to help you with your problem.**

Please report security issues to security@brew.sh.

This is our PGP key which is valid until June 17, 2016.

* Key ID: `0xE33A3D3CCE59E297`

* Fingerprint: `C657 8F76 2E23 441E C879 EC5C E33A 3D3C CE59 E297`

* Full key: https://keybase.io/homebrew/key.asc

Homebrew's current maintainers are [Misty De Meo](https://github.com/mistydemeo), [Andrew Janke](https://github.com/apjanke), [Xu Cheng](https://github.com/xu-cheng), [Mike McQuaid](https://github.com/mikemcquaid), [Baptiste Fontaine](https://github.com/bfontaine), [Brett Koonce](https://github.com/asparagui), [Martin Afanasjew](https://github.com/UniqMartin), [Dominyk Tiller](https://github.com/DomT4), [Tim Smith](https://github.com/tdsmith) and [Alex Dunn](https://github.com/dunn).

Former maintainers with significant contributions include [Jack Nagel](https://github.com/jacknagel), [Adam Vandenberg](https://github.com/adamv) and Homebrew's creator: [Max Howell](https://github.com/mxcl).

Code is under the [BSD 2 Clause (NetBSD) license](https://github.com/Homebrew/homebrew/tree/master/LICENSE.txt).

Documentation is under the [Creative Commons Attribution license](https://creativecommons.org/licenses/by/4.0/).

Homebrew is a non-profit project run entirely by unpaid volunteers. We need your funds to pay for software, hardware and hosting around continuous integration and future improvements to the project. Every donation will be spent on making Homebrew better for our users.

Homebrew is a member of the [Software Freedom Conservancy](http://sfconservancy.org) which provides us with an ability to receive tax-deductible, Homebrew earmarked donations (and [many other services](http://sfconservancy.org/members/services/)). Software Freedom Conservancy, Inc. is a 501(c)(3) organization incorporated in New York, and donations made to it are fully tax-deductible to the extent permitted by law.

- [Donate with PayPal](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=V6ZE57MJRYC8L)

- Donate by USA $ check from a USA bank:

- Make check payable to "Software Freedom Conservancy, Inc." and place "Directed donation: Homebrew" in the memo field. Checks should then be mailed to:

- Software Freedom Conservancy, Inc.

137 Montague ST STE 380

BROOKLYN, NY 11201 USA

- Donate by wire transfer: contact accounting@sfconservancy.org for wire transfer details.

- Donate with Flattr or PayPal Giving Fund: coming soon.

Our CI infrastructure was paid for by [our Kickstarter supporters](https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Kickstarter-Supporters.md).

Our CI infrastructure is hosted by [The Positive Internet Company](http://www.positive-internet.com).

Our bottles (binary packages) are hosted by Bintray.

[](https://bintray.com/homebrew)

Homebrew is a member of the [Software Freedom Conservancy](https://sfconservancy.org)

[](https://sfconservancy.org)

Some formulae should not go in

[homebrew/core](https://github.com/Homebrew/homebrew-core). But there are

additional [Interesting Taps & Branches](Interesting-Taps-&-Branches.md) and anyone can start their

own!

Stuff that comes with OS X or libraries that are provided by

[RubyGems, CPAN or PyPi](Gems,-Eggs-and-Perl-Modules.md)

should not be duplicated. There are good reasons for this:

* Duplicate libraries regularly break builds

* Subtle bugs emerge with duplicate libraries, and to a lesser extent,

duplicate tools

* We want our formulae to work with what comes with OS X

There are exceptions:

* OpenSSL - Apple has formally deprecated OpenSSL on OS X in favour of their own Security Framework

& consequently the OS X OpenSSL is rarely updated and frequently falls behind important security updates.

Homebrew endeavours to use our shipped OpenSSL as much

as possible.

* Programs that a user will regularly interact with directly, like editors and

language runtimes

* Libraries that provide functionality or contain security updates not found in

the system version

* Things that are **designed to be installed in parallel to earlier versions of

themselves**

Formula | Reason

--- | ---

ruby, python, perl | People want newer versions

bash | OS X's bash is stuck at 3.2 because newer versions are licensed under GPLv3

zsh | This was a mistake, but it’s too late to remove it

emacs, vim | [Too popular to move to dupes](https://github.com/Homebrew/homebrew/pull/21594#issuecomment-21968819)

subversion | Originally added for 10.5, but people want the latest version

libcurl | Some formulae require a newer version than OS X provides

openssl | OS X's openssl is deprecated & outdated.

libxml2 | Historically, OS X's libxml2 has been buggy

We also maintain [a tap](https://github.com/Homebrew/homebrew-dupes) that

contains many duplicates not otherwise found in Homebrew.

Software that can upgrade itself does not integrate well with Homebrew's own

upgrade functionality.

Because that circumvents our hash-checks, makes finding/fixing bugs

harder, often breaks patches and disables the caching. Almost always you

can add a resource to the formula file to handle the

separate download and then the installer script will not attempt to load

that stuff on demand. Or there is a command line switch where you can

point it to the downloaded archive in order to avoid loading.

Our policy is that formulae in the core repository

([homebrew/core](https://github.com/Homebrew/homebrew-core)) must be built

from source (or produce cross-platform binaries like e.g. Java). Binary-only

formulae should go to [homebrew/binary](https://github.com/Homebrew/homebrew-binary) or [homebrew-cask](https://github.com/caskroom/homebrew-cask).

Formulae in the core repository must have a stable version tagged by

the upstream project. Tarballs are preferred to git checkouts, and

tarballs should include the version in the filename whenever possible.

Software that only provides a development/beta, tagged version should be put in

[homebrew/devel-only](https://github.com/Homebrew/homebrew-devel-only).

We don’t accept software without a tagged version because they regularly break

due to upstream changes; we can’t provide [bottles](Bottles.md) for them; and

we don’t have an automatic update mechanism for `head-only` formulae which

makes them very quickly outdated.

First check that there is not already a binding available via

[`gem`](https://rubygems.org/) or [`pip`](http://www.pip-installer.org/)

etc..

If not, then put bindings in the formula they bind to. This is more

useful to people. Just install the stuff! Having to faff around with

foo-ruby foo-perl etc. sucks.

The software in question must be

* maintained (e.g. upstream is still making new releases)

* known

* stable (e.g. not declared "unstable" or "beta" by upstream)

* used

* have a homepage

We will reject formulae that seem too obscure, partly because they won’t

get maintained and partly because we have to draw the line somewhere.

We frown on authors submitting their own work unless it is very popular.

Don’t forget Homebrew is all `git` underneath! Maintain your tap if you have to!

There may be exceptions to these rules in the main repository, we may

include things that don't meet these criteria or reject things that do.

Please trust that we need to use our discretion based on our experience

running a package manager.

Don’t make your formula build an `.app` (native OS X Application); we

don’t want those things in Homebrew. Make it build a command line tool

or a library. However, we have a few exceptions to that, e.g. when the

App is just additional to CLI or if the GUI-application is non-native

for OS X and/or hard to get in binary elsewhere (example: fontforge).

Check out the [homebrew-cask](https://github.com/caskroom/homebrew-cask)

project if you’d like to brew native OS X Applications.

Even if all criteria are met we may not accept the formula.

Documentation tends to lag behind current decision-making. Although some

rejections may seem arbitrary or strange they are based from years of

experience making Homebrew work acceptably for our users.