Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release vaultenv to Hackage #92

Open
cdepillabout opened this issue Mar 8, 2020 · 0 comments
Open

release vaultenv to Hackage #92

cdepillabout opened this issue Mar 8, 2020 · 0 comments

Comments

@cdepillabout
Copy link

cdepillabout commented Mar 8, 2020

It would be convenient for Linux distributions if vaultenv were released to Hackage.

There is already an issue about this (#1), but it has been closed with this last comment:

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

One thing that wasn't mentioned in #1 is that uploading to Hackage can sometimes help Linux distributions package vaultenv.

Some Linux distributions (including NixOS) have an automated process for building and updating Haskell packages that are uploaded to Hackage.

Since vaultenv is not uploaded to Hackage, it has to be updated by hand.

This isn't difficult, but it is a manual step we have to perform. vaultenv is sometimes out of date because no one realizes it need to be updated. If vaultenv was on Hackage, then we wouldn't have to do this.


Also, uploading packages to Hackage is relatively easy for the maintainers of the package (just stack upload), so hopefully it wouldn't be imposing too much.

(Although, there are other well-known packages that choose not to upload to Hackage. For instance spago is one I know well. So it is not like it is completely unheard of not uploading to Hackage.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant