Fixes for a couple of regressions discovered while packaging riak-3.2.0:
When riak was started via systemctl, the .service unit file had riak foreground (blindly following an advice from riak launcher script generated by rebar3.18), which resulted in pipe files in /tmp/erl_pipes/riak@127.0.0.1 not being created as they should be for riak attach to work. Whether it is a bug or feature in relx that comes with rebar3.18, is a matter for rebar3 developers to comment or investigate; for the time being, changing the starting command (back) to riak start appears to be sufficient.
If riak launcher script finds an empty VMARGS_PATH, it extracts node from the default vm.args which will always be set to "riak@127.0.0.1", while the proper value, as specified in /etc/riak.conf, is to be found in generated.conf/vm.*.args. It's probably cuttlefish's task to take care of it by exporting VMARGS_PATH, but it doesn't currently do so, meaning we should do it ourselves.
An optimisation that allows packagers (me) to reuse previously fetched deps and avoid downloading 100s of megs every time make package is run (similar optimisations have already been included for deb and rpm flavors).
An update of vars.config for alpine that should have been included in #1114 but wasn't.
Fixes for a couple of regressions discovered while packaging riak-3.2.0:
riak foreground(blindly following an advice from riak launcher script generated by rebar3.18), which resulted in pipe files in /tmp/erl_pipes/riak@127.0.0.1 not being created as they should be forriak attachto work. Whether it is a bug or feature in relx that comes with rebar3.18, is a matter for rebar3 developers to comment or investigate; for the time being, changing the starting command (back) toriak startappears to be sufficient.nodefrom the default vm.args which will always be set to "riak@127.0.0.1", while the proper value, as specified in /etc/riak.conf, is to be found in generated.conf/vm.*.args. It's probably cuttlefish's task to take care of it by exporting VMARGS_PATH, but it doesn't currently do so, meaning we should do it ourselves.make packageis run (similar optimisations have already been included for deb and rpm flavors).