root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 1 Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Jean-Sébastien Pédron 2019-06-27 15:33:50 +02:00
parent c45cd8fd74
commit 6252d33317
No known key found for this signature in database
GPG Key ID: 39E99761A5FD94CC
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
mk/rabbitmq-mix.mk
View File

@ -3,7 +3,7 @@
# those Elixir applications to build even with no access to Hex.pm,
# using the bundled sources only.
HEX_OFFLINE = 1
HEX_OFFLINE := 1
# mix(1) centralizes its data in `$MIX_HOME`. When unset, it defaults
# to something under `$XDG_DATA_HOME`/`$XDG_CONFIG_HOME` or `$HOME`
@ -11,6 +11,11 @@ HEX_OFFLINE = 1
#
# We store those data for offline build in `$(DEPS_DIR)`.
override MIX_HOME = $(DEPS_DIR)/.mix
override MIX_HOME := $(DEPS_DIR)/.mix
export HEX_OFFLINE MIX_HOME
# In addition to `$MIX_HOME`, we still have to set `$HOME` which is used
# to find `~/.hex` where the Hex.pm cache and packages are stored.
override HOME := $(DEPS_DIR)
export HEX_OFFLINE MIX_HOME HOME