[snoyberg]

This is false, see the `stack solver` and `stack init --solver` commands. Currently it's using cabal's dependency solver under the surface, but there is work in progress (by multiple parties) to implement a new SAT-based solver, see: https://github.com/commercialhaskell/stack/issues/116

[mightybyte]

Ahh, my mistake. Cabal's solver is in the cabal-install package and since stack doesn't depend on it I assumed it wasn't tackling that problem.

Since it's actually shelling out to the cabal executable for its solving needs it still pretty much fits the definition of porcelain.