Download/Install Script for Binary

[joehand]

With #115 we have binaries being built on each new tagged release.

However, we still need to make it easy to "install" this. We've used this script with dat: https://github.com/datproject/dat/blob/master/download.sh and can take a similar approach.

• Add download/install script
• Document install methods (via npm or via install script)
• Add install methods to website

[joehand]

For some documentation fodder, see https://zeit.co/download.sh

[joehand]

See https://gist.github.com/joehand/24f15a88c13dc628fd3dc459d9810429 for an install script and some open questions also added below.

Questions I have:

• Is ~/.cabal/releases the best place to install?
• Can we make that exit message nicer?
• What if the latest release isn't published? (this happened in Dat because we released a new one but the binary didn't get built b/c tests failed causing this script to break)
• Should we prefer this distribution to npm? (e.g. zeit/now installs the binary when you do npm install)

[cblgh]

Is ~/.cabal/releases the best place to install?

yeah that's a good spot :)

Can we make that exit message nicer?

on fail? or what exit message

What if the latest release isn't published? (this happened in Dat because we released a new one but the binary didn't get built b/c tests failed causing this script to break)
Should we prefer this distribution to npm? (e.g. zeit/now installs the binary when you do npm install)

oh hm, i don't think i have any opinions on these. @noffle?

[hackergrrl]

@joehand I'm ok with letting people use their distribution's package manager to install cabal, and just providing the ZIP archives with the binaries for folx who want to DIY it.