Changing an option's default or existence can trigger repouring the bottle unnecessarily

[ilovezfs]

A source build may be triggered when it's unwanted or unneeded if

• an install receipt (using the option) is present that was created when the option default was different
  or
• another formula's depends_on "foo" => "with-bar" was authored when the option default was different

Typically the option "with-bar" has been replaced by "without-bar" or by nothing (because it's now always on, always off, no longer applicable, or now hidden behind a build.with? or build.without?).

A related issue is that there's no mechanism in the DSL to specify a default-on option is mandatory, so simply making a stale "with-bar" into a no-op (rather than an unneeded source build) is still pretty bad because it gives the impression that "bar" is being mandated, but "surprisingly" a keg in the Cellar built "without-bar" (a real, current formula option) would satisfy a no-op "with-bar" in depends_on "foo" => "with-bar".

[ilovezfs]

Based on what was reported in Homebrew/homebrew-core#7753 it seems this is still happening with dependency build options since depends_on "llvm" => "with-nosuchoption" behaves differently from depends_on "llvm".