Commit graph

5 commits

Author SHA1 Message Date
Vítor Galvão
83c712741b Merge branch 'strip_launcher_from_names' of https://github.com/rolandwalker/homebrew-cask into rolandwalker-strip_launcher_from_names
Conflicts:
	Casks/googleappengine.rb
	doc/CASK_NAMING_REFERENCE.md
2015-01-29 13:54:06 +00:00
Roland Walker
9cb0b1cfdf expand @ symbols in tokens
refs: #8478
2014-12-29 09:41:47 -05:00
Roland Walker
e01ef5058a generate_cask_token Ruby 2.0 shebang line
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
2014-12-11 11:15:52 -05:00
Roland Walker
cb5a40f787 remove constraint that tokens can't start w/ digit
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.
2014-12-05 11:54:56 -05:00
Roland Walker
a335d3b06d unify and recast "Cask name" & "title" as "token"
* "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.
2014-12-01 11:00:23 -05:00
Renamed from developer/bin/cask_namer (Browse further)