They are unused now, since rabbit is provided as an .ez archive.
While here, don't copy include files as well: they are not enough to
build a RabbitMQ plugin anyway.
We can do because Cuttlefish is now used as a library and configuration
is managed at runtime by the RabbitMQ node, not by a preliminary
execution of cuttlefish(1).
but not 23.0. By being overly conservative with minor version numbers
we repeatedly run into the same problem:
* A RabbitMQ release comes out and marks 22.1 as unsupported
* Erlang/OTP 22.1 comes out the next day
* Debian users cannot install this combination which the docs unintentionally
recommend by using the "latest 22" apt compoonent.
Minor versions of 21.x and 22.x have been compatible with the original
major release, so let's switch to a more optimistic version range
unless we have evidence of incompatibilities in recent minor releases.
`$MIX_HOME` is used by mix(1) (for `~/.mix` equivalent). But the Hex
plugin does not use this variable to store `~/.hex`. Instead, it
apparently still relies on `$HOME` only.
So set and export both variables.
If I understand the code correctly, it should be enough to point mix(1)
to the packages we add to the source archive for offline build.
There should be no need to mess with `$HOME` or `$XDG_*_HOME`.
Exactly like we do it with `$HOME`, this is to exercices our hack to
make mix(1) work offline.
Starting with Elixir 1.9.0, mix(1) accepts a `$MIX_HOME` variable to
point it to its own central directory. If it's not defined, it uses
first the `$XDG_DATA_HOME` and `$XDG_CONFIG_HOME` Freedesktop.org
variables. Then it uses `$HOME`.
So here, we specify those two variables explicitely to make sure they do
not disturb the build process.
... by using the `override` directive to enforce our internal value.
As a reminder, this a hack to convince mix(1) to work offline and use a
copy of the Hex.pm cache provided in the source archive.
Note that this file was moved from rabbitmq-common. It has no use there
and it avoids the need to go through the entire CI pipeline if we want
to change this file.
The `stats.mk` file was also moved to the new `mk` subdirectory to avoid
file pollution at the root of this project.