Local no-index repositories cache leads to bad UX · haskell/cabal#9136

(5 留言) (0 反應) (0 負責人)Haskell (1,731 star) (732 fork)batch import

good first issuere: user experiencetype: enhancement

描述

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

Provide a better caching mechanism, detecting changes to the local repository.
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.

貢獻者指南

技術棧: 無
領域: clideveloper experiencetooling
議題類型: bug
難度: 3
預計時間: 1-3 hours
活動狀態: stale
清晰度: clear
前置要求: Knowledge of cabal configurationAbility to read Haskell codeFamiliarity with caching mechanisms
新手友善度: 55
研究方向: Review the cabal documentation on local no index repositories to understand the caching behavior. Examine the cabal source code, likely in the Cabal or cabal install modules, to find where the cache file is written and read. Implement a warning message to remind the user to delete the cache if the repository changes, as an alternative to the more complex caching improvement. Issue #9133 provides additional context.