Hi Jacky,
> I deleted the tag 2.7-rc1 and kept 2.7rc.1 to keep the consistence.
Thank you! This allowed me to update the homebrew cask for
openrefine-dev, and homebrew caskroom maintainers accepted my PR:
https://github.com/caskroom/homebrew-versions/pull/3319
Now OpenRefine 2.7RC1 can be installed on macOS by installing Homebrew
(directions at
http://brew.sh) and running this:
brew cask install openrefine-dev
This installs OpenRefine.app in the "/Applications" folder. If an
existing OpenRefine.app is found, homebrew will not overwrite it, so
installing via homebrew requires either deleting or renaming
previously installed copies.
By the way, I'll be happy to continue maintaining OpenRefine recipes
for homebrew. Once a new stable version is released, the caskroom
approach would be as follows:
1. Add a new caskroom recipe, "openrefine" - with the current stable
version (I assume this spelling is preferable to "open-refine"?)
2. Delete "openrefine-dev" until a new RC is created, at which point
version-specific casks would be created, e.g., "openrefine-2.8"
(deleting this once 2.8 is released as stable.
3. Delete "google-refine", as this will no longer be the current
stable version of the software.
Also, I should mention for those confused by homebrew vs. caskroom,
"caskroom" is the homebrew extension project where pre-built binaries
and GUI applications go, whereas the original, plain old "homebrew"
project is reserved for command-line utilities that can be built from
source. So OpenRefine clearly belongs in caskroom.
Joe