1. Summary

It would be nice if users could run Vale commands immediately after installation.

2. Argumentation of the need for the feature

Note that Vale as such is not included in this package but downloaded the first time you execute vale.

Currently, users need to add the postinstall step for downloading Vale to their pipelines. This is the extra step in configuring. Technically, I can’t understand why users need to do it.

3. Technical details

3.1. Installation process

As far as I understand, the package should do the following: download the latest Vale version → unzip the Vale binary to the folder added to the $PATH in the needed environment. Is the postinstall step really needed to do it? Or am I missing something?

3.2. gh-release-install

This spring I was looking for a package manager for GitHub releases and found gh-release-install written in Python. In my opinion, it’s far from being considered a perfect package manager, but it still makes coding easier. Perhaps its use will assist in resolving the problem described in this issue.

3.3. The example of possibly desired behavior

For one of my Python projects I needed to add binaries of fd and my own build of HTML Tidy to the directory for binaries. I wrote the script gh_release_install.py (yes, I know it doesn’t verify checksums and architectures). Perhaps its structure will seem simpler to you than functions extract_vale() and download_vale_if_missing().

Thanks.