Even when we make sound decisions while creating packages, we still find ourselves needing to update them.
We may update these packages to accommodate changing requirements or to configure a new feature recently added to the control panel.
Unfortunately, this causes all website override settings to revert to an "inherited" state.
If overrides aren't permanent, there’s no real point in using them.
A better approach would be to include an option when updating packages: "Do not touch website override settings that are higher."
This way, only those override settings that are lower than the new values would revert to an "inherited" state.