This script runs `brew cask audit` on any Casks added or modified in the
given range of commits. If the `url` or `sha256` stanzas have been
modified and `sha256` is not `:no_check`, run the audit with
`--download` to verify the checksum.
* convert existing Cask:: namespace to Hbc::
* move Homebrew-fork code under Hbc::
* move freestanding classes such as Tty and TopologicalHash under Hbc::
* recast HOMEBREW_CASK_ constants as HBC_
* modify our Homebrew Formula for backward compatibility
* devscripts and dev docs
It was just carelessness that this script was written in
a way limited to Ruby 2.0, but we may as well be explicit
about that pending a fix.
closes#8021
Class names are now completely hidden from the user. This
commit works by adding a prefix to all Cask class names, which
is considered to be an ugly transitional hack on the way to
representing individual Casks as instances.
* "Canonical App Name" becomes "Simplified App Name"
* devscript `cask_namer` renamed to `generate_cask_token`
* doc file `CASK_NAMING_REFERENCE.md` renamed to `cask_token_reference.md`
* DSL uses `"#{token}"` for interpolation instead of `"#{title}"`
* documentation text
* backend code (variables, method, class names)
* error message text
* tests
* code comments
* Cask comments
* emphasize `tags :name`
* doc: use "vendor" consistently instead of "developer"
* doc: many man page argument descriptions were incorrect
* incidental clarifications
Many backend variables similar to `cask_name` or `cask` have
been standardized to `cask_token`, `token`, etc, resolving a long-
standing ambiguity in which variables named `cask` might contain
a Cask instance or a string token.
In many places the docs could be shortened from "Cask name" to
simply "token", which is desirable because we use the term "Cask"
in too many contexts.
Almost all of these two scripts are identical. Refactor out the common
bits, saving over 60 lines of repetition.
Right now this is handled by moving all the logic into "develop_brew_cask"
and symlinking "production_brew_cask".
This will be followed by another patch to add a "manage_brew_cask_links"
command to do the same with sub-commands, e.g.,
manage_brew_cask_links status
returns "production" or "develop",
manage_brew_cask_links production
does the same as production_brew_cask,
manage_brew_cask_links develop
does the same as develop_brew_cask, etc. At that point, I'd like to
rename the script "manage_brew_cask_links" and have the two present
names be symlinked to that.
This was motivated by (besides DRY) getting tired of having to
manually check symlinks to see which state I was currently in.
based on lessons learned from failed release v0.39.0,
`git push && git push --follow-tags` is smarter because
it reduces the chance of an unreleasable tag being pushed.
(git pushes the tags before it pushes the commits).
Zhiming Wang