# 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:** 36

<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: [April 7, 2024, 10:04am UTC](https://discourse.haskell.org/t/does-cabal-update-force-recompilation-of-everything/8010/36 "2024-04-07T10:04:33Z")

</div>

> [@atravers](#):
>
> But it surely couldn’t be that simple - there must be some other major points of difference between Cargo and Cabal…

I guess personal preferences. On pretty much every Rust video there are jokes about `cargo` being very slow and downloading way too many dependencies (which looks exactly like my original complaint with `cabal`)

I just wish there would be a command like `cabal build --develop` which picks the plan which minimizes rebuilds/downloads. This is a minimal use case (and apparently solved by using a freeze file), at this point many user would _prefer_ “pick latest” and others “pick fastest”, but again: it is a matter of personal preference.

I will try using freeze files and see how good/bad they are. Probably I’ll still have problems between projects. Example: project A and project B uses same dependency set, but `cabal` picks different versions on each project for whatever reason.

I think there is no point to keep the discusion open without proposing any real solution. So I am asking to close it if that’s ok. @f-a may you close it?

---

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