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
With Homebrew/homebrew-bundle#1418 there is now an easy command available to check if any brews, casks, vscodes would be removed by --cleanup. I was thinking about adding another option for homebrew.onActivation.cleanup (perhaps "check"?), which simply fails the pre-activation checks if the system is not in sync with the generated Brewfile (could also be used with darwin-rebuild check without actually performing uninstalls). For now I have something like this in my own config, but thought it seemed like it might be useful enough to upstream; it also relies on some internal options to work:
Would a PR adding this as a first-class option be accepted? If so, I wasn't sure whether it should be another choice for onActivation.cleanup, or a separate option like homebrew.onActivation.checkCleanup. I could see wanting something like this, but I'm not sure if there's any precedent for options like this that have different outcomes during check vs switch:
{homebrew.onActivation={checkCleanup=true;# only fails `darwin-rebuild check`cleanup="zap";# invokes --zap on `darwin-rebuild switch`};}
The text was updated successfully, but these errors were encountered:
With Homebrew/homebrew-bundle#1418 there is now an easy command available to check if any brews, casks, vscodes would be removed by
--cleanup
. I was thinking about adding another option forhomebrew.onActivation.cleanup
(perhaps"check"
?), which simply fails the pre-activation checks if the system is not in sync with the generated Brewfile (could also be used withdarwin-rebuild check
without actually performing uninstalls). For now I have something like this in my own config, but thought it seemed like it might be useful enough to upstream; it also relies on some internal options to work:Would a PR adding this as a first-class option be accepted? If so, I wasn't sure whether it should be another choice for
onActivation.cleanup
, or a separate option likehomebrew.onActivation.checkCleanup
. I could see wanting something like this, but I'm not sure if there's any precedent for options like this that have different outcomes duringcheck
vsswitch
:The text was updated successfully, but these errors were encountered: