# Does cabal update force recompilation of everything?

**URL:** <https://discourse.haskell.org/t/does-cabal-update-force-recompilation-of-everything/8010>\
**Category:** Uncategorized\
**Created:** [November 5, 2023, 9:31pm UTC](https://discourse.haskell.org/t/does-cabal-update-force-recompilation-of-everything/8010 "2023-11-05T21:31:09Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![Lsmor](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/lsmor/32/3302_2.png) [@Lsmor](https://discourse.haskell.org/u/Lsmor)\
**Post date:** [November 9, 2023, 9:50am UTC](https://discourse.haskell.org/t/does-cabal-update-force-recompilation-of-everything/8010/20 "2023-11-09T09:50:38Z")

</div>

This is the reason I don’t run `cabal update` so often. You have to wait for both `cabal` and `hls` to fully build your project after it… It makes developing not fun… which is the main reason I programm in Haskell. Of course, cabal should **not** aim for fun but for stability and reproducibility, so I guess the correct behaviour is the current.

Nevertheless, I could imagine `cabal build --develop` to be a “just take the plan for whatever is downloaded or cached.” But now, we are approaching again to [this other thread](http://discourse.haskell.org/t/an-external-command-system-for-cabal-what-would-you-do-with-it/7114)

---

_[View the full topic](https://discourse.haskell.org/t/does-cabal-update-force-recompilation-of-everything/8010)._
