hledger/stack.yaml

# cf https://github.com/commercialhaskell/stack/wiki/stack.yaml

resolver: lts-3.0

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

flags:

extra-deps:
- vty-5.3.1
tools: stack yaml cleanup 2015-08-23 19:36:42 +03:00			`# cf https://github.com/commercialhaskell/stack/wiki/stack.yaml`

			`resolver: lts-3.0`

add a stack.yaml, using today's stackage nightly 2015-06-17 23:57:15 +03:00			`packages:`
			`- hledger-lib`
			`- hledger`
ui: revive the curses UI, now named hledger-ui 2015-08-13 21:22:40 +03:00			`- hledger-ui`
add a stack.yaml, using today's stackage nightly 2015-06-17 23:57:15 +03:00			`- hledger-web`
tools: stack yaml cleanup 2015-08-23 19:36:42 +03:00
			`flags:`

cli: a more robust and featureful bench test The bench script invoked by cabal bench or stack bench now links the benchmarked code directly, avoiding any dependence on the shell and $PATH. Also, it reports the journal parse time and the various reports on the parsed data separately, and runs quicker. You can get more accurate benchmark times by running with --criterion. This will usually give much the same numbers and takes much longer. Benchmarking via simplebench is still available, by running with --simplebench. In this mode it benchmarks whatever commands are configured in bench/default.bench. A disadvantage is that it uses the first "hledger" executable in $PATH, so check which one it reports. 2015-06-26 01:54:45 +03:00			`extra-deps:`
ui: revive the curses UI, now named hledger-ui 2015-08-13 21:22:40 +03:00			`- vty-5.3.1`