Author: Greg Pfeil <greg@technomadic.org>
Committer: GitHub <noreply@github.com>
Explain reason for `brew-api` flake input I had inadvertently left out `brew-api` when I set up `brew-nix`. I only noticed because on a recent `home-manager switch` with a new cask added, evaluation failed because the version in brew-nix’s pinned `brew-api` input was no longer available. This hopefully makes it clear why a user should set up `brew-api`, even though they do nothing with it besides override another flake’s input. Another suggestion is that `brew-api` might be more clearly named `brew-formulae` or something that makes it clear it’s the data source for `brew-nix` and not something more static, like an API definition.
| Time to Start | Worker time | Duration | Time to finish | |
| Config | 0s | 1s | 1s | 1s |
| Eval | 2s | 2s | 2s | 4s |
| Build | - | - | - | - |
| Test | - | - | - | - |
| Deploy | - | - | - | - |
| Suite | 0s | 3s | 3s | 4s |