Commit Graph

4 Commits

Author SHA1 Message Date
Jean-Sébastien Pédron 6b337b49c7 Use {MIX,HEX}_HOME variables to prepare offline cache
We used to use $HOME for both tools, but they now support dedicated
variables. As an added bonus, this makes the recipe work on Microsoft
Windows.
2021-04-13 14:43:32 +02:00
Jean-Sébastien Pédron 6252d33317
rabbitmq-mix.mk: Still set `$HOME` in addition to `$MIX_HOME`
`$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.
2019-06-27 15:33:50 +02:00
Jean-Sébastien Pédron c45cd8fd74
rabbitmq-mix.mk: Set `$MIX_HOME` instead of `$HOME`
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`.
2019-06-27 15:02:20 +02:00
Jean-Sébastien Pédron 68213819aa
rabbitmq-mix.mk: Ensure `$HOME` does not come from the command line
... 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.
2019-06-26 18:34:20 +02:00