Local no-index repositories cache leads to bad UX

[andreabedini]

Describe the bug

It's documented that, when using local no-index repositories.

cabal-install creates a .cache file, and will aggressively use its contents if it exists. Therefore if you change the contents of the directory, remember to wipe the cache too.

but cabal-install offers no warning or message about this leaving the user staring, confused, at a solver failure. See for example #9133.

Expected behavior

Cabal should either

1. Provide a better caching mechanism, detecting changes to the local repository.
2. Remnind the user that it will only look at the cache file and that the user should manually delete the cache file if the repository has changed.

[danse]

Regarding #9133, i think i built the one failing package like the others. Maybe i rebuilt it, i do not think i changed the version. When i was inspecting the sdist dirs, i thought that the noindex.cache and the tar.gz files were both outcomes of cabal v2-install. Maybe, if it is not too expensive, could be worth always regenerating the noindex.cache when the command succeeds