Last active
April 30, 2016 00:21
-
-
Save borsboom/6f0af7db3682e481a3c8c416ad8d31f3 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
\begin{hcarentry}{(The Stack build tool)} | |
\report{Emanuel Borsboom} | |
\status{stable} | |
\label{stack} | |
\makeheader | |
Stack is a modern, cross-platform build tool for Haskell code. It is intended for | |
Haskellers both new and experienced. | |
Stack handles the management of your toolchain (including GHC — the Glasgow | |
Haskell Compiler — and, for Windows users, MSYS), building and registering | |
libraries, building build tool dependencies, and more. While it can use existing | |
tools on your system, Stack has the capacity to be your one-stop shop for all | |
Haskell tooling you need. | |
The primary design point is reproducible builds. If you run \texttt{stack build} | |
today, you should get the same result running \texttt{stack build} tomorrow. | |
There are some cases that can break that rule (changes in your operating system | |
configuration, for example), but, overall, Stack follows this design philosophy | |
closely. To make this a simple process, Stack uses curated package sets called | |
snapshots. | |
Stack has also been designed from the ground up to be user friendly, with an | |
intuitive, discoverable command line interface. | |
Since its first release in June 2015, many people are using it as their primary | |
Haskell build tool, both commercially and as hobbyists. New features and | |
refinements are continually being added, with regular new releases. | |
Binaries and installers/packages are available for common operating systems to | |
make it easy to get started. Download it at \url{http://haskellstack.org/}. | |
\FurtherReading | |
\url{http://haskellstack.org/} | |
\end{hcarentry} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment