Should I use the stack to build and load in Hackage?

Over time, I developed a Haskell installation, confusing at the system level, which I do not know how to completely clean up . But for the most part, this is not a big concern, as I just use stack to manage Haskell configurations for each project. However, since my project requirements diverge from my Haskell system, I am wondering what is the best way to create and download packages for Hackage.

In particular (1) should be used

stack exec -- cabal sdist
stack exec -- cabal upload

instead of simple

cabal sdist
cabal upload

and (2) should there be some reason to install the cabal project version (c stack build cabal?)

Or is there a more efficient approach to building and distributing stack based Hackage that is not directly invoked cabal?

+4
source share
1 answer

Adding an answer based on my previous comment.


stack offers equivalent functionality through
  • stack sdist
  • stack upload

which do not require interaction with cabaldirectly in projects based on the stack.

A complete list of commands supported by the stack can be obtained through:

$ stack --help

and official documentation .

Individual commands also support --helpto see which command line flags they support.

+4
source

Source: https://habr.com/ru/post/1665163/


All Articles