{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiasykiyz5mqwbk5dnc6e33w4ixpggypbloblb5zusdvnbkelrgbc4",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mhfabanc45s2"
  },
  "path": "/t/users-of-stack-and-nix-seeking-feeback-on-sensible-defaults/13826#post_1",
  "publishedAt": "2026-03-18T22:43:41.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "Users of both Stack and the Nix package manager, I am seeking feedback on sensible defaults for Stack, as follows:\n\n  * On the NixOS operating system, Stack’s Nix integration is currently enabled by default. Is that still sensible? I understand that the Nix project advises Stack users not to use its Nix integration, but take a different route.\n\n  * Stack’s Nix integration, when enabled, implies `--system-ghc` (prefer a ‘system’ GHC executable on the PATH (e.g. one in the Nix environment) to a Stack-supplied GHC executable) and `--install-ghc` (seek to download and install the specified GHC version, if it is not already available). Is `--install-ghc` a sensible default with Nix integration? Should it be `--no-install-ghc` (eg fail, if Nix does not have the specified GHC version)?\n\n\n\n\nMore radically, is anyone actually using Stack’s Nix integration? I’ve been asked to consider dropping it. However, I would not contemplate that if people are using it; Stack’s Nix integration is easy to support and does not ‘get in the way’ for non-users of the integration.",
  "title": "Users of Stack and Nix: seeking feeback on sensible defaults"
}