Skip to content

Commit 9ad9284

Browse files
committed
Merge pull request #284 from exercism/homebrew-release-docs
Update the homebrew release instructions
2 parents 1be950f + f8681ce commit 9ad9284

1 file changed

Lines changed: 29 additions & 16 deletions

File tree

RELEASE.md

Lines changed: 29 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -73,31 +73,44 @@ Check out a feature branch, where X.Y.Z is the actual version number.
7373
$ git checkout -b exercism-vX.Y.Z
7474
```
7575

76-
Calculate the `SHA1` checksum for the two mac builds:
76+
## Update Homebrew
7777

78-
```plain
79-
$ openssl sha1 release/exercism-mac-32bit.tgz
80-
$ openssl sha1 release/exercism-mac-64bit.tgz
78+
This is helpful for the (many) Mac OS X users.
79+
80+
First, get a copy of the latest tarball of the source code:
81+
82+
```
83+
cd ~/tmp && wget https://github.com/exercism/cli/archive/vX.Y.Z.tar.gz
8184
```
8285

83-
Update the homebrew-binary/exercism.rb formula.
86+
Get the SHA256 of the tarball:
8487

85-
- version
86-
- urls
87-
- `SHA1` checksums
88+
```
89+
shasum -a 256 vX.Y.Z.tar.gz
90+
```
8891

89-
If you are on a mac, you can test the formula by running:
92+
Update the formula:
9093

91-
```plain
92-
$ brew unlink exercism && brew install ./exercism.rb
9394
```
95+
cd $(brew --repository)
96+
git checkout master
97+
git remote add YOUR_USERNAME git@github.com:YOUR_USERNAME/homebrew.git
98+
brew update
99+
git checkout -b exercism-vX.Y.Z
100+
brew edit exercism
101+
# update sha256 and tarball url
102+
brew audit exercism
103+
brew install exercism
104+
brew test exercism
105+
git commit -m "exercism X.Y.Z"
106+
git push --set-upstream YOUR_USERNAME exercism-vX.Y.Z
107+
```
108+
109+
Then go to https://github.com/Homebrew/homebrew and create pull request.
94110

95-
Then submit a pull request to homebrew-binary. Note that they're very, very careful about their
96-
commit history. If you made multiple commits, squash them. They don't merge using the button on
97-
GitHub, they merge by making sure that the branch is rebased on to the most recent master, and
98-
then they do a fast-forward merge. That means that the PR will be red when it's closed, not purple.
111+
Note that they really don't want any verbose commit messages or PR descriptions when all you're doing is bumping a version.
99112

100-
Also, don't bother trying to DRY out the formula, they prefer having explicit, hard-coded values.
113+
For more information see their [contribution guidelines](https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/How-To-Open-a-Homebrew-Pull-Request-(and-get-it-merged).md#how-to-open-a-homebrew-pull-request-and-get-it-merged).
101114

102115
## Update the Docs Site
103116

0 commit comments

Comments
 (0)