"Freeze" the state of the package DB? #2996

Closed
edsko opened this Issue Dec 25, 2015 · 5 comments

Projects

None yet

3 participants

@edsko
Contributor
edsko commented Dec 25, 2015

It's somewhat annoying when using cabal-nix that whenever I call cabal update, a subsequent cabal-nix might start installing a bunch of new packages. (Somewhat related to @hvr 's way-back feature.)

@hvr
Member
hvr commented Dec 25, 2015

Btw I actually love that cabal new-build rebuilds stuff against the latest versions by default, some stuff I'm working on relies on this very property. Freezing the package db should be something the user explicitly requests (e.g. by writing something like hackage-snapshot: 2015-12-24T14:43 into the cabal.project file).

@edsko
Contributor
edsko commented Dec 25, 2015

Ah, yes, I'm not suggesting freezing should happen by default.

@hvr
Member
hvr commented Dec 25, 2015 edited

I hope I'll get to forward-porting the index-wayback branch very soon so we can glue it all together and see how it interoperates with nix-local-build, cabal.project & hackage-security

PS: See #3604

@edsko
Contributor
edsko commented Jan 25, 2016

Note that always defaulting the latest and greatest of all packages also means we end up with tons of different permutations of packages with their dependencies in the store. Still not convinced that this is the most sensible default.

@ezyang
Contributor
ezyang commented Aug 24, 2016

There is now cabal new-freeze which should have the desired effect.

@ezyang ezyang closed this Aug 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment