![brew cask install specific version brew cask install specific version](https://miro.medium.com/max/2020/1*7l2uoVi8j36mukcqC6ktyA.png)
![brew cask install specific version brew cask install specific version](https://pawelgrzybek.com/photos/2018-07-05.jpg)
It would also lead to other issues, since some casks (like brackets) have different executable names for every version, further polluting the link parameter. We couldn’t also reliably provide that feature (few apps have all the older versions publicly available for the taking), and managing that would be extremely hard (sometimes pull requests to this project are for apps that weren’t updated in a long while, we don’t really care about what came in between, nor do I think we should, for the aforementioned reasons). The hack way of installing a old version of cask formula would be: cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask, go the place where cask is referenced git reset -hard c3c1b84b7a, this would effective set chromedriver to v.36 git checkout -b temp, checkout a new branch, which prevents brew auto-refresh your local master brew install -cask chromedriver, this would install your desired version. brew search jdk Find adoptopenjdk8 in the casks brew cask info adoptopenjdk8 Confirm information about the cask. brew tap homebrew/cask-versions cask-versions must be tapped to get access to this caskto different cask versions. A GUI application is an app that you can see running, as opposed to invisibly running in the background. I don’t want to stretch this too much, but access to older versions is a very niche option, and there are already websites dedicated to that. Another option is installing AdoptOpenJDK 8 via cask. brew refers to Homebrew, which you just installed.cask refers to Homebrew Cask, an extension to Homebrew that is used to install GUI application on your computer.(GUI stands for 'Graphical User Interface'. The issue you mentioned ( #142) is about providing support for different types of versions - nightly builds and the like - and you’re correct, your proposed functionality is something different altogether. brew install git uses the Homebrew package (called a formula) while brew cask install git uses the Homebrew Cask package (called a cask). I don’t think that idea fits with the overall goal of homebrew-cask this project is about providing a simple, straight-forward way of of installing applications, not providing “every feature under the sun”. Homebrew and Homebrew Cask are separate projects run by different teams. Writing this on a tiny keyboard, so bear with me (even on vacation, I can’t seem to leave this project).