# Download
## A. I want to download a packaged version
Packaged versions may lag behind the latest release, but are the quickest to install.
|
|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| **Windows:** | Download and run the [latest development builds](developer-guide.html) (-> Appveyor CI)
| **Mac:** | `brew install hledger`
| **Debian, Ubuntu:** | `sudo apt install hledger hledger-ui hledger-web`
| **Fedora, RHEL:** | `sudo dnf install hledger`
| **Gentoo:** | `sudo layman -a haskell && sudo emerge hledger hledger-ui hledger-web`
| **NixOS:** | `nix-env -iA nixpkgs.haskellPackages.hledger \`
`nixpkgs.haskellPackages.hledger-ui \`
`nixpkgs.haskellPackages.hledger-web`
Only some of the hledger tools may be available, eg Homebrew does not yet include
hledger-ui, hledger-web or hledger-api (packagers welcome!).
## B. I want to build the latest release
The latest release (see [release notes](release-notes.html)) is a good choice.
You have to build it, but that's pretty easy.
1. Install [`stack`](http://haskell-lang.org/get-started).
On Windows, the 64-bit version is [recommended](https://github.com/simonmichael/hledger/issues/275#issuecomment-123834252).
2. `stack install --resolver=nightly hledger [hledger-ui] [hledger-web] [hledger-api]`\
On Windows, hledger-ui is [not yet available](https://github.com/coreyoconnor/vty/pull/1).\
If stack says you need to run `stack setup`, do that first.\
Warnings about "No packages found in snapshot which provide a "hsc2hs" executable" can be ignored.\
If required C libraries (like curses) are not installed, you might need to install those manually and try again, eg:
|
|--------------------|-----------------------------------
| **Debian, Ubuntu:** | `sudo apt install libncurses5-dev`
| **Fedora, RHEL:** | `sudo dnf install ncurses-devel`
3. If stack warns that `~/.local/bin` (or the Windows equivalent) is not in `$PATH`, fix that.
Eg if you're a bash user:\
`echo "export PATH=$PATH:~/.local/bin" >> ~/.bashrc && source ~/.bashrc`\
Now you can run `hledger --version`, `hledger-ui --version` etc.
Installing with [`cabal`](https://www.haskell.org/cabal/) is similar, if you're familiar with that.
## C. I want to build the [development version](https://github.com/simonmichael/hledger/commits/master)
The dev version includes not-yet-released features and is stable enough for daily use.
1. Install [`stack`](http://haskell-lang.org/get-started) and [git](https://en.wikipedia.org/wiki/Git)
2. `git clone http://code.hledger.org hledger`
3. `cd hledger`
4. `stack install`\
with the same caveats as mentioned above:
- if stack says you need to run `stack setup`, do that first,
- if building fails due to missing C libs, install those first
- if stack warns that `~/.local/bin` (or the Windows equivalent) is not in `$PATH`, fix that
- warnings about "No packages found in snapshot which provide a hsc2hs executable" can be ignored
Cabal users can use the `cabal-install.sh` or the `cabal.project` files instead.
