* Add install/update instructions database
* Update the database
* Revert README changes
They will be overwritten later.
* Revert
* Tweak
* Tweaks
* Upgrade database
* Complete commands
Still not sure about Spack upgrades.
* Sort
* Doc generation script draft
* Remove OS names from tool names
* Fix Linuxbrew name
* `wheel` already installs `setuptools`
* Gen docs
* Update
* Tweak
* Add a GitHub workflow to check for outdated installation instructions
* Fix return value
* Test
* Delete test
* Rename the script
* Add `make doc-install-inst`
* Add missing dev requirement
* The first tool is the primary we want to display
Then they are simply sorted by `tool.title`.
* Sort OSes by name
* Refactoring, jinja template, etc.
* Add tool title uniqueness `assert`, fix platform list extra `\n`
* Rebuild docs
* Update generate.py
* Update README.md
* Update methods.yml
* Update distros derived, more assertions
* Tweaks
* Add workflow to auto-update the docs
* Do not hide the command
* Tweaks
Co-authored-by: Jakub Roztocil <jakub@roztocil.co>
Use of the `personal-files` interface is reserved for vetted publishers.
The interface requires a validation, but we need to publish at least
one package first. So let's skip that part, release a version and ask
for the interface access in a second time.
Also add a workflow to build & test the snap package.
* Add a workflow to check documentations
* Fix markdown issues
* Install Ruby 2.7
* Finally, handle and fix GitHub templates
* Minor improvement in the feature request template
* Verbose mode to be sure all files are checked
* Split the monolithic workflow into specific ones
* Rename workflows, improve commands
* Update pip from the venv
* Fix Windows setup
* Lowercase macos-latest
* Fix Windows run, again
* Update brew formula to 2.5.0
* Can use `idna` 3.2
* Sort requirements to ease reproductible builds
And also to have the same output as `brew bump-formula-pr`.
* Sync `bottles` with official Formula
And keep the `high_sierra` one.
* Add a workflow to check the Formula
* Remove hashbang from bash completion
Completion files are not supposed to have a hashbang.
They are sourced, not executed.
* Fix spelling
* Trim excess whitespace
Running tests through `python setup.py test` is deprecated:
> WARNING: Testing via this command is deprecated and will be removed
> in a future version. Users looking for a generic test entry point
> independent of test runner are encouraged to use tox.
I am not in favor of moving back to `tox`, we should simply run tests
using `python -m pytest` (or `make test`) and that's it.
A new extra was added, `dev`, to install development requirements:
$ python -m pip install --upgrade --editable '.[dev]'
