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

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

22 lines
754 B
Makefile
Raw Permalink Normal View History

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-27 00:34:20 +08:00
# This file is copied to rabbitmq_cli (and possibly other Elixir-based
# components) when the RabbitMQ source archive is created, to allow
# those Elixir applications to build even with no access to Hex.pm,
# using the bundled sources only.
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 21:33:50 +08:00
HEX_OFFLINE := 1
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-27 00:34:20 +08:00
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 21:02:20 +08:00
# mix(1) centralizes its data in `$MIX_HOME`. When unset, it defaults
# to something under `$XDG_DATA_HOME`/`$XDG_CONFIG_HOME` or `$HOME`
# depending on the Elixir version.
#
# We store those data for offline build in `$(DEPS_DIR)`.
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-27 00:34:20 +08:00
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 21:33:50 +08:00
override MIX_HOME := $(DEPS_DIR)/.mix
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 21:02:20 +08:00
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-08 16:50:39 +08:00
# In addition to `$MIX_HOME`, we still have to set `$HEX_HOME` which is used to
# find `~/.hex` where the Hex.pm cache and packages are stored.
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 21:33:50 +08:00
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-08 16:50:39 +08:00
override HEX_HOME := $(DEPS_DIR)/.hex
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 21:33:50 +08:00
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-08 16:50:39 +08:00
export HEX_OFFLINE MIX_HOME HEX_HOME