You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dependencies:
brew:
- tflint@311029c24de3de608e78afe0ee4f2413ea7a792b # this is tflint release 0.18.0 in brew's formulae
Usage of @
Using the @ might be tricky, because there are actually some brew packages that have names with @ in them to denote versions, e.g.:
$ pwd
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core
$ ls Formula/openssl*
Formula/[email protected]
Option 1
ops could look for a package like this, and only try to use it as a git ref if a package with that name doesn't already exist in Homebrew. This might be too much trouble.
Option 2
Another option is to allow an expanded format of the depedency:
One brew dependency there is a hash, and one is a string. This also might be too much trouble.
Option 3
A third option is to use a character other than @. While ruby uses @, pip uses ==, and apt uses =. It might not be counterintuitive for developers to use =.
The text was updated successfully, but these errors were encountered:
Looks like
brew
just usesgit
to pull packages and build them, andops
could check out a specific commit hash or branch:https://stackoverflow.com/questions/39187812/homebrew-how-to-install-older-versions
Usage of
@
Using the
@
might be tricky, because there are actually some brew packages that have names with@
in them to denote versions, e.g.:Option 1
ops
could look for a package like this, and only try to use it as a git ref if a package with that name doesn't already exist in Homebrew. This might be too much trouble.Option 2
Another option is to allow an expanded format of the depedency:
One
brew
dependency there is a hash, and one is a string. This also might be too much trouble.Option 3
A third option is to use a character other than
@
. While ruby uses@
, pip uses==
, and apt uses=
. It might not be counterintuitive for developers to use=
.The text was updated successfully, but these errors were encountered: