Skip to content
This repository has been archived by the owner on Apr 25, 2020. It is now read-only.

Usage of package-db stack inconsistent (Cradle vs. cabal-helper) #505

Closed
DanielG opened this issue Jul 5, 2015 · 3 comments
Closed

Usage of package-db stack inconsistent (Cradle vs. cabal-helper) #505

DanielG opened this issue Jul 5, 2015 · 3 comments
Milestone

Comments

@DanielG
Copy link
Owner

DanielG commented Jul 5, 2015

We're still using the package-db stack from cradle in a bunch of places, that's going to lead to trouble!

Related: #504

@DanielG DanielG added this to the Next release milestone Jul 5, 2015
@ajnsit
Copy link

ajnsit commented Jul 8, 2015

Can you help me understand this issue? I am basically using cradle package db stacks for "stack" (the executable, damn it's confusing) support. But this issue seems to indicate that I should move to using cabal-helper.

@DanielG
Copy link
Owner Author

DanielG commented Jul 8, 2015

Basically right now when we're using cabal-helper, i.e. whenever there is a .cabal file, the cradle package-db stack is going to be completely wrong in some cases because that just uses the pre cabal-helper guessing logic instead of using cabal-helper to extract the package-db from LocalBuildInfo: http://hackage.haskell.org/package/Cabal-1.22.4.0/docs/Distribution-Simple-LocalBuildInfo.html#v:withPackageDB

@DanielG
Copy link
Owner Author

DanielG commented Aug 7, 2015

Fixed by 8439f12

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants