Please see the README.md for usage information, and
the wiki on Github for more details. Also, note that
the API for the library is not currently stable, and may
change significantly, even between minor releases. It is
currently only intended for use by the executable.
[
Skip to Readme]
Versions |
0.0.0, 0.0.1, 0.0.2, 0.0.2.1, 0.0.3, 0.1.0.0, 0.1.0.0, 0.1.1.0, 0.1.2.0, 0.1.3.0, 0.1.3.1, 0.1.4.0, 0.1.4.1, 0.1.5.0, 0.1.6.0, 0.1.8.0, 0.1.10.0, 0.1.10.1, 1.0.0, 1.0.2, 1.0.4, 1.0.4.1, 1.0.4.2, 1.0.4.3, 1.1.0, 1.1.2, 1.2.0, 1.3.0, 1.3.2, 1.4.0, 1.5.0, 1.5.1, 1.6.1, 1.6.1.1, 1.6.3, 1.6.3.1, 1.6.5, 1.7.1, 1.9.1, 1.9.1.1, 1.9.3, 1.9.3.1, 2.1.1, 2.1.1.1, 2.1.3, 2.1.3.1, 2.3.1, 2.3.3, 2.5.1, 2.5.1.1, 2.7.1, 2.7.3, 2.7.5, 2.9.1, 2.9.3, 2.9.3.1, 2.11.1, 2.13.1, 2.15.1, 2.15.3, 2.15.5, 2.15.7, 3.1.1, 9.9.9 |
Change log |
ChangeLog.md |
Dependencies |
aeson (>=0.8.0.2), async (>=2.0.2), attoparsec (>=0.12.1.5), base (>=4.7 && <5), base16-bytestring, base64-bytestring, bifunctors (>=4.2.1), binary (>=0.7), bytestring (>=0.10.4.0), Cabal (>=1.18.1.5), conduit (>=1.2.4), conduit-combinators (>=0.3.1), conduit-extra (>=1.1.7.1), containers (>=0.5.5.1), cryptohash (>=0.11.6), cryptohash-conduit, deepseq, directory (>=1.2.1.0), either, enclosed-exceptions, exceptions (>=0.8.0.2), fast-logger (>=2.3.1), file-embed, filepath (>=1.3.0.2), hashable (>=1.2.3.2), http-client (>=0.4.9), http-client-tls (>=0.2.2), http-conduit (>=2.1.5), http-types (>=0.8.6), lifted-base, monad-control, monad-logger (>=0.3.13.1), monad-loops (>=0.4.2.1), mtl (>=2.1.3.1), old-locale (>=1.0.0.6), optparse-applicative (>=0.11.0.2), optparse-simple (>=0.0.3), path (>=0.5.1), persistent (>=2.1.2), persistent-sqlite (>=2.1.4), persistent-template (>=2.1.1), pretty, process (>=1.2.0.0), resourcet (>=1.1.4.1), safe (>=0.3), split, stack, stm (>=2.4.4), streaming-commons (>=0.1.10.0), tar (>=0.4.1.0), template-haskell, temporary (>=1.2.0.3), text (>=1.2.0.4), time (>=1.4.2), transformers (>=0.3.0.0), transformers-base (>=0.4.4), unix (>=2.7.0.1), unordered-containers (>=0.2.5.1), vector (>=0.10.12.3), vector-binary-instances, void (>=0.7), word8, yaml (>=0.8.10.1), zlib (>=0.5.4.2) [details] |
License |
BSD-3-Clause |
Author |
Chris Done |
Maintainer |
chrisdone@fpcomplete.com |
Category |
Development |
Home page |
https://github.com/commercialhaskell/stack
|
Source repo |
head: git clone https://github.com/commercialhaskell/stack |
Uploaded |
by borsboom at 2015-06-23T16:49:21Z |
stack
is a cross-platform program for developing Haskell
projects. It is aimed at Haskellers both new and experienced.
It features:
- Installing GHC automatically.
- Installing packages needed for your project.
- Building your project.
- Testing your project.
- Benchmarking your project.
How to install
Downloads are available by operating system:
How to use
Go into a Haskell project directory and run stack build
. If everything is
already configured, this will:
- Download the package index.
- Download and install all necessary dependencies for the project.
- Build and install the project.
You may be prompted to run some of the following along the way:
stack new
to create a brand new project.
stack init
to create a stack configuration file for an existing project.
stack will figure out what Stackage release (LTS or nightly) is appropriate
for the dependencies.
stack setup
to download and install the correct GHC version. (For
information on installation paths, please use the stack path
command.)
Run stack
for a complete list of commands.
Architecture
A full description of the architecture
is available here.
Questions, Feedback, Discussion
- For frequently asked questions about detailed or specific use-cases,
please see
the FAQ.
- For general questions, comments, feedback and support please write
to the stack mailing list.
- For bugs, issues, or requests please
open an issue.
Why stack?
stack is a project of the Commercial Haskell
group, spearheaded by FP Complete. It is
designed to answer the needs of commercial Haskell users, hobbyist Haskellers,
and individuals and companies thinking about starting to use Haskell. It is
intended to be easy to use for newcomers, while providing the customizability
and power experienced developers need.
While stack itself has been around since June of 2015, it is based on codebases
used by FP Complete for its corporate customers and internally for years prior.
stack is a refresh of that codebase combined with other open source efforts
like stackage-cli to meet the needs of
users everywhere.
A large impetus for the work on stack was a large survey of people interested
in
Haskell,
which rated build issues as a major concern. The stack team hopes that stack
can address these concerns.