hledger/stack8.2.yaml

# stack build plan using GHC 8.2.2

nix:
  pure: false
  packages: [perl gmp ncurses zlib]

resolver: lts-11.22

packages:
- hledger-lib
- hledger
- hledger-ui
- hledger-web

# TODO: some of these were for hledger-api and can be removed
extra-deps:
# use the latest base-compat with all ghc versions
- aeson-1.3.1.1
- ansi-terminal-0.10.3
- base-compat-0.10.1
- base-compat-batteries-0.10.1
- cassava-megaparsec-2.0.0
- config-ini-0.2.3.0
- criterion-1.4.1.0
- doctest-0.16.3
- megaparsec-7.0.1
- parser-combinators-1.0.0
- process-1.6.5.1
- swagger2-2.2.2
# avoid no hashable instance for AccountName from doctests
- hashtables-1.2.3.1
# avoid https://github.com/simonmichael/hledger/issues/791
- directory-1.3.2.2
# hledger-ui
# newer fsnotify has a different api and may be more robust
- fsnotify-0.3.0.1
- tasty-1.2.3
- tasty-hunit-0.10.0.2
- wcwidth-0.0.2
- ansi-wl-pprint-0.6.9
- wai-handler-launch-3.0.3.1
- streaming-commons-0.2.1.2
- network-2.7.0.0
- math-functions-0.3.3.0
stack: cleanups 2018-03-24 18:49:36 +03:00			`# stack build plan using GHC 8.2.2`
don't symlink stack.yaml, I think windows doesn't like it 2016-10-22 03:58:17 +03:00
;stack-8.2/4/6: ensure new-enough wai-handler-launch [ci skip] 2020-03-02 02:01:09 +03:00			`nix:`
			`pure: false`
			`packages: [perl gmp ncurses zlib]`

;stack: bump to latest ghc 8.2, 8.4 snapshots 2019-07-13 01:26:16 +03:00			`resolver: lts-11.22`
use nix integration option 2017-12-09 15:23:03 +03:00
don't symlink stack.yaml, I think windows doesn't like it 2016-10-22 03:58:17 +03:00			`packages:`
			`- hledger-lib`
			`- hledger`
			`- hledger-ui`
			`- hledger-web`
tools: add easytest (github) as an extra dep, for experiments 2018-02-16 03:30:50 +03:00
;api: another round of hledger-api purging; fix the build 2019-09-12 00:49:22 +03:00			`# TODO: some of these were for hledger-api and can be removed`
tools: add easytest (github) as an extra dep, for experiments 2018-02-16 03:30:50 +03:00			`extra-deps:`
make older ghcs mostly work with new base-compat (#794) Using the same base-compat version across all ghc versions is kind of the point of base-compat; now we can rely on whatever base-compat 0.10.1 provides. hledger-api has been commented with ghc 7.10, way too much hassle. 2018-06-05 00:54:24 +03:00			`# use the latest base-compat with all ghc versions`
			`- aeson-1.3.1.1`
cli: --color/--colour option; smart emacs, windows autodetection (#1296) 2020-07-14 22:08:36 +03:00			`- ansi-terminal-0.10.3`
make older ghcs mostly work with new base-compat (#794) Using the same base-compat version across all ghc versions is kind of the point of base-compat; now we can rely on whatever base-compat 0.10.1 provides. hledger-api has been commented with ghc 7.10, way too much hassle. 2018-06-05 00:54:24 +03:00			`- base-compat-0.10.1`
			`- base-compat-batteries-0.10.1`
lib: switch to megaparsec 7 2018-09-30 04:32:08 +03:00			`- cassava-megaparsec-2.0.0`
			`- config-ini-0.2.3.0`
make older ghcs mostly work with new base-compat (#794) Using the same base-compat version across all ghc versions is kind of the point of base-compat; now we can rely on whatever base-compat 0.10.1 provides. hledger-api has been commented with ghc 7.10, way too much hassle. 2018-06-05 00:54:24 +03:00			`- criterion-1.4.1.0`
;enable doctest with ghc 8.10 2020-03-31 01:28:11 +03:00			`- doctest-0.16.3`
lib: switch to megaparsec 7 2018-09-30 04:32:08 +03:00			`- megaparsec-7.0.1`
			`- parser-combinators-1.0.0`
;deps: explicit process extra-dep for ghc 8.2 also 2019-07-13 10:12:44 +03:00			`- process-1.6.5.1`
make older ghcs mostly work with new base-compat (#794) Using the same base-compat version across all ghc versions is kind of the point of base-compat; now we can rely on whatever base-compat 0.10.1 provides. hledger-api has been commented with ghc 7.10, way too much hassle. 2018-06-05 00:54:24 +03:00			`- swagger2-2.2.2`
use newer hashtables to fix an instance warning with doctests/ghc 7 (#794) 2018-06-05 03:02:57 +03:00			`# avoid no hashable instance for AccountName from doctests`
			`- hashtables-1.2.3.1`
make older ghcs mostly work with new base-compat (#794) Using the same base-compat version across all ghc versions is kind of the point of base-compat; now we can rely on whatever base-compat 0.10.1 provides. hledger-api has been commented with ghc 7.10, way too much hassle. 2018-06-05 00:54:24 +03:00			`# avoid https://github.com/simonmichael/hledger/issues/791`
stack: try latest directory for a startup hang with windows symlinks 2018-05-30 20:33:25 +03:00			`- directory-1.3.2.2`
ui: support/require fsnotify 0.3.0.1+ The api has changed, it supports directory events, and might be more robust. 2018-06-05 16:41:13 +03:00			`# hledger-ui`
			`# newer fsnotify has a different api and may be more robust`
			`- fsnotify-0.3.0.1`
;stack: update extra deps in old stack yamls 2019-11-29 02:07:09 +03:00			`- tasty-1.2.3`
			`- tasty-hunit-0.10.0.2`
			`- wcwidth-0.0.2`
			`- ansi-wl-pprint-0.6.9`
;stack-8.2/4/6: ensure new-enough wai-handler-launch [ci skip] 2020-03-02 02:01:09 +03:00			`- wai-handler-launch-3.0.3.1`
			`- streaming-commons-0.2.1.2`
			`- network-2.7.0.0`
require newer Decimal, math-functions, fixing inconsistent rounding Decimal 0.5.1+ changed to banker's rounding (round to nearest even number), and math-functions 0.3.3.0 (used by roi) fixed various precision-related issues. Now we require the latest versions of these. This was causing some functional test failures when building with old GHCs/snapshots. 2020-03-19 20:10:55 +03:00			`- math-functions-0.3.3.0`