Arranging auxiliary tasks for a Haskell project -
there repetitive auxiliary tasks have run when developing or testing project. example: downloading data, setting database, cleaning logs, etc. in ruby land, handled rake
while other languages prefer make
or else (tasks depend on other tasks, may need 1 task perform subtasks depends on).
so, is there conventional way organize tasks in haskell project?
i assume cabal
used that, not of auxiliary tasks running haskell code: it's case of performing rm -r logs/*.log
or downloading data wget
or curl
. make sense make cabal's test
target depend on other cabal targets that, ugh, run shell scripts/commands haskell code? (if it's possible have dependent targets in cabal @ all?)
alternatively, use make
, "an average haskeller" (an "outside" project contributor, example) find intuitive? believe 1 first try cabal test
before discovering requires setting database testing first, running whole chain of other tasks. 1 notice makefile
in first place?
i couldn't find recipes handling auxiliary tasks in haskell project around.
as long know, there's no de facto standard tool in haskell project.
but heard shake, monadic build system written in haskell.
Comments
Post a Comment