TorBrowser #162
Closed
TorBrowser #162
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
There's a mismatch between the filename and the cask name; see #146 (comment) for an explanation. I fixed it while merging. Re: 32-bit versions… I'm not too sure, but both #125 and #142 should help. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've added two new Casks for TorBrowser on OS X for x86_64. One is the normal stable branch that most users should use and the other is our alpha release channel.
I'm not sure of the best way to add the 32bit releases to the same Cask files - is there a way that you plan to do this? Or should I just create torbrowser-i386 and torbrowser-alpha-i386 or should I just forget that 32bit architectures exist? :)