* Update msys installer to latest stable release (#756)

* Update msys installer to latest stable release

* Alr.Platforms.Windows: new msys2 installer doesn't need extra script

Co-authored-by: Fabien Chouteau <chouteau@adacore.com>

* Bump version to 1.0.1

* Fixes for GNAT CE2021

Co-authored-by: Fabien Chouteau <chouteau@adacore.com>

* Color commands in alr [help] and display in groups

* Prevent Getopt from intercepting -h and --help

* Change formatting of command and global options help

* Fix test equivalent_help

* Only print title if there are more than zero options

* user-changes.md: document SPDX license expressions

* Typo

* Another typo

Co-authored-by: Alejandro R. Mosteo <amosteo@unizar.es>

This will help users identify what is new since the last release.

* Implement narrowing down of new "any" dependencies

Instead of adding just a foo* dependency, check how it was solved and use that
version to add a more precise (and usually wanted) dependency; e.g., foo^1.2,
foo~0.1

* Fix case of dependency removal

* New test and fixed other tests to new behavior

Many tests explicitly check the added dependencies, so this is extra assurance
about this change.

* Recognize the wildcard as "any" version

* Document user-visible changes

* Add option to disable new behavior

Use a fixed version instead of latest on master branch of msys2-installer.
Changes in the master branch can break our installation code.

* Attempt fix at windows temporaries

* Remove now superfluous exception handler

* Review fix

* Update documentation

* Warn when adding a ^0.x dependency

* Warn on suspicious caret use

This warning is shown at most once per run, and is an optional blocker during
`alr with` and `alr publish`.

A new `Alire.Warnings` package allows simple emission of warnings only once.

* Improve comment wording

* Document user-visible changes

* Rebase fixes

* Make the Warning Id its own type

https://github.com/msys2/msys2-installer/pull/20 changed the name of the argument for installation prefix of the msys2 installer.
All previous versions are impacted and won't be able to install msys2 at the correct location.

* Rename `alr list` to `alr crates`

This way there is less confusion about the purposes of `alr crates` and `alr
search`; the former operates on crates and the latter on releases.

* Fix bash completion

* Document user-visible changes

* Remove `crates` command, move to `search --crates`

* Update bash completion for new situation

* Update user-facing document

* Updated testsuite

* Remove old references to [general] section

* Clarify running moments of actions

* Separate non-preelaborable parts of Config

These parts are now in Alire.Config.Edit

* Fixes for Windows-specific sources

This should exclude false positives for actual alire sources in a child folder.

* Remove use of build/clean relocations

* Document user-facing visible changes

#664

* Alire.Properties.Licenses: Add support of SPDX expression

The legacy license support is still available but will trigger warning
messages.

* Update catalog-format-spec.md

* Add support for custom license ID

* Update catalog-format-spec.md

* Update alire.toml

* tests/index/bad-license-too-long: fix index version

* Detect wrong enum values only in local manifests

This allows backwards compatibility for the index, but catches user mistakes.

* New `alr index --check`, check unknown enum values

* Testsuite: proper behavior of enum checks

* Document user-facing changes

* Add handling of CentOS, Fedora, Red Hat and their package manager (#20)

* Transform Redhat version scheme into semver one (#20)

* RPM: Take epochs into account for versions

Co-authored-by: Alejandro R. Mosteo <amosteo@unizar.es>

This flag filters out packages installed indirectly (as dependencies), causing
our detection of such a package to fail. -Q by design already only works on
installed packages, so that's all we need.

For embedded ZFP run-time this warning will pop everywhere.

* Fix pacman pkg detection to consider epochs

* Relaxed parsing for Pacman versions

* Bump index version to devel-0.5

The addition of more enum values to support other distributions is a
breaking change. This raises the question of whether we should simply drop
unknown enum values, as this could well work. But then, using an improper value
would silently fail. Perhaps the warning could be disabled for normal use and
re-enabled for publish?

* Fix python formatting (missing empty lines)

* Alr.Commands.Withing: Be able to compose paths

* Testsuite: test for the bugfix

* Better feedback on malformed hash in index

Fix .gitignore so only the root /alire is ignored

* Fix for breaking change in used action

* Workflow to test with unsupported package manager

* Add config option to disable distro detection

With test

* Fixes for circular elaboration

* Fix test for slight change in behavior

Before the last changes to break circularities, we tried to load the manifest
as part of the config loading process. Now we are satisfied with finding a
properly named file at the expected place. This causes one test to not detect
invalid TOML, since the manifest contents aren't really needed for the test.

* Solver: Speed-up for impossible dependencies

Whenever a solution is incomplete we keep looking for solutions. But if the
reason for incompleteness is an impossible request (non-existent crate or
version), this resulted on finding all combinations for the rest of crates that
do have satisfiable dependencies.

With this patch, impossible situations are considered part of the "complete"
solution (as there cannot be a more complete one), which allows the solver to
use complete the search much more quickly, as no pointless attempts for more
solutions are made.

* Fixes for problems caught by the test suite

The optimization was too aggressive, as it took place before detecting
externals. Also, it should only apply to direct unavoidable dependencies, as
indirect impossibilities can be avoided by other solutions.

Simply return distro unknown

* ci-windows.yml: replace add-path command

see https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

* ci-windows,yml: use bash shell

Otherwise the changes are listed without context and it's a bit confusing.

If we are only using git to generate the archive, we do not need the remote as
it won't be referenced by the origin.