forked from awakesecurity/gRPC-haskell
-
Notifications
You must be signed in to change notification settings - Fork 3
/
stack.yaml
61 lines (48 loc) · 2.16 KB
/
stack.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
# This file was automatically generated by stack init
# For more information, see: http://docs.haskellstack.org/en/stable/yaml_configuration/
# Specifies the GHC version and set of packages available (e.g., lts-3.5, nightly-2015-09-21, ghc-7.10.2)
resolver: lts-14.1
# Local packages, usually specified by relative directory name
packages:
- '.'
- 'core'
# Override default flag values for local packages and extra-deps
flags: {}
# Extra package databases containing global packages
extra-package-dbs: []
extra-deps:
- git: git@github.com:awakesecurity/proto3-suite.git
commit: 3f6dd6f612cf2eba3c05798926ff924b0d5ab4fa
- git: git@github.com:awakesecurity/proto3-wire.git
commit: 4f355bbac895d577d8a28f567ab4380f042ccc24
# Control whether we use the GHC we find on the path
#
# NB: It is important that this is `false`, because we do NOT want `stack` to
# use our nix-built ghc which is used in the `nix`/`cabal` worfklows, we want it
# to use its own LTS version. Setting this to `true` and then trying to run
# tests via `stack` inside the `nix-shell` will result in some cryptic package
# collison messages: e.g., there's a `text` in the nix-built ghc which are
# using, and another `text` in what `stack` wants to use.
system-ghc: false
# Require a specific version of stack, using version ranges
# require-stack-version: -any # Default
# require-stack-version: >= 1.0.0
# Override the architecture used by stack, especially useful on Windows
# arch: i386
# arch: x86_64
# Extra directories used by stack for building
# extra-include-dirs: [/path/to/dir]
# extra-lib-dirs: [/path/to/dir]
# Allow a newer minor version of GHC than the snapshot specifies
# compiler-check: newer-minor
# NB: We really only rely on Nix integration for creating the environment for
# running tests. Thus `stack --nix test` can be used to run the tests. However,
# since this will rebuild a custom ghc often due to the structure of
# release.nix, it is suggested that `nix-shell release.nix -A grpc-haskell.env`
# is used and then `stack test` (sans `--nix`) is used during development and
# test iterations.
nix:
enable: false
pure: false
shell-file: release.nix
nix-shell-options: ["-A", "grpc-haskell.env"]