Open cdalvaro opened 1 month ago
This is the method that is used to load installed casks in the brew info
command. It just grabs all directories in the caskroom and uses the base name of each of them to parse the token. Since this particular token is ambiguous (it's in multiple taps) and we're using the short token, it falls back to the first cask with a matching token which happens to be the one in homebrew/cask
.
We do store the original caskfile that was used during installation so we could potentially try to get the full token from there. At the end of the day, this sort of situation will eventually be elegantly handled by adding an install receipt for casks (see https://github.com/Homebrew/brew/issues/17013).
brew doctor
outputVerification
brew doctor
output" above saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
twice and am still able to reproduce my issue.brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.brew config
outputWhat were you trying to do (and why)?
I'm trying to list all my installed formulae and casks, and looking for their corresponding taps using the command:
brew info --json=v2 --installed
.However, I have discovered that casks from custom taps have
homebrew/cask
as the assigned tap. (This may only happens with casks that are also available from thehomebrew/cask
tap. Currently, I only have two casks in my custom tapcdalvaro/tap
, but they are available at the official repository too).I'm improving the
mac_brew_pkg
module for salt (https://github.com/saltstack/salt/pull/66611) and I have encountered this issue writing some tests.What happened (include all command output)?
After installing a cask from a custom tap:
The tap information is wrong when it is queried using:
brew info --json=v2 --installed
What did you expect to happen?
I expected to see
cdalvaro/tap
as the tap for thesalt
cask.Step-by-step reproduction instructions (by running
brew
commands)