{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidelfi3wnld3kexdblommkqi3oyfrkkpubhiwhzsdu5m2htyyd2e4",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjuwp77bl5l2"
  },
  "path": "/t/simple-per-project-setup/12930?page=2#post_37",
  "publishedAt": "2026-04-19T19:54:08.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "GitHub - mise-plugins/mise-ghcup: An asdf plugin wrapping GHCup. · GitHub",
    "aqua-registry/pkgs/haskell at main · aquaproj/aqua-registry · GitHub"
  ],
  "textContent": "I’m trying to get something similar working, as I’ve only had extremely positive experiences with using `mise` for Python (`uv`), Rust, TypeScript (`yarn`) and Golang management per-project. I’ve gotten to the point where I only keep `python@3.13` in my global, and all other language-specific compilers/tooling are per-project.\n\nCan I ask how you managed to pin GHC with mise? As I see, the old asdf format plugin (GitHub - mise-plugins/mise-ghcup: An asdf plugin wrapping GHCup. · GitHub) is archived and not maintained, and the replacement aqua registry format (aqua-registry/pkgs/haskell at main · aquaproj/aqua-registry · GitHub) only has the ability to pin GHCup and cabal, not GHC directly.",
  "title": "Simple per-project setup"
}