Useless and harmful advice to reconfigure given when saved package config cannot be read

[andreasabel]

I sometimes see the advice given here:

cabal/Cabal/src/Distribution/Simple/Configure.hs

Lines 156 to 158 in a97e1f1

	dispConfigStateFileError ConfigStateFileNoParse =
	text "Saved package config file is corrupt."
	<+> text "Re-run the 'configure' command."

Running cabal configure as advised has never solved the problem, but instead on top destroyed my cabal.project.local (#8408). (Nothing but removing the build folder has helped me so far.)

I never run cabal configure in production (just cabal build directly), so why should this help? Rather, if cabal encounters some corrupt saved configuration upon cabal build it should execute cabal build as if there were no saved configuration lying around.

[Mikolaj]

This advice is for v1- and/or Setup mode of operation, right? Does it only appear when using those? Is it correct for those (if we change it to cabal v1-configure)?