Put vaultenv on hackage

[arianvp]

No description provided.

[ruuda]

What is the advantage of putting binaries (as opposed to libraries) on Hackage?

[arianvp]

stack install vaultenv

[arianvp]

It's just another way for people to get the binary. A lot of haskell-related tools are installed this way (stack, intero, hlint, cabal, etc) however, vaultenv is not really a haskell-related tool of course...

[ruuda]

I oppose to using language-specific package managers for general-purpose tools. Too often I come across a project that seems interesting, with a section in the readme

Installation

$obscure_package_manager_i_have_never_heard_of install $some_package

No thanks, I don’t want yet another package manager that I need to install, and that I need to remember to update regularly. There is already a system package manager for that.

Packaging for all the different system package managers is a pain for developers, true. But installing and keeping up to date fifteen different package managers is a pain for users.

[arianvp]

Okay so it's either that or:

$obscure_package_manager_i_have_never_heard_of build
cp ~/.stack/work/weird-directory-structure/x86_64/bin/vaultenv ~/.local/bin

I don't really see the difference, except that you still need to download stack And now need extra steps.

What we could do is provide a binary distrubtion when we tag releases though... this is possible through Github

[no-longer-on-githu-b]

With Travis you can automatically upload binaries to GitHub with not too much effort

[duijf]

What we could do is provide a binary distrubtion when we tag releases though... this is possible through Github

The current release process is to put binaries on the GH releases page, so I think this can be closed.

If anyone sees this and has requests wrt to the release process, please open a new ticket :)