epmd, nodetool, releases and scripts about relx

[kosmon]

I'd like this as well. I can't include ERTS because I'm building the release on a platform different than the deployment target. But, I still need nodetool and install_upgrade.escript so I have to copy them separately into the target ERTS dir.

[tsloughter]

Taking a look today.

[tsloughter]

Please checkout the branch of that pull request to see if it works for you. I did a quick test locally. I don't think it assuming epmd isn't started is an issue, but I did move the scripts to the bin dir and updated the script to use them from there.

So hopefully fixes your issues and doesn't break anything else :)

[kosmon]

Thank you Tristan, I will test this out when I get back to my office on
Tuesday.

Nick

On Sat, Jan 18, 2014 at 8:08 AM, Tristan Sloughter <[email protected]

wrote:

Please checkout the branch of that pull request to see if it works for
you. I did a quick test locally. I don't think it assuming epmd isn't
started is an issue, but I did move the scripts to the bin dir and updated
the script to use them from there.

So hopefully fixes your issues and doesn't break anything else :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-32685307
.

[opensam]

Hello,

I made git clone --branch mvoe_nodetool_install_upgrade git://github.com/tsloughter/relx
I cd'ed to it and ran make (ok). I got a new (testing) relx executable.
Then I pointed the RELX of my makefile to the new relx executable.
I set {include_erts, false} as I wish it.
The new relx made a release successfully (as the previous one) withOUT ERTS.
I tested
appname start
appname attach
appname stop
and the 3 worked OK for me :-)
Thank you Tristan. I appreciate the improvement of relx.

I hope Tristan's patch is OK for all and can be merged.
BTW I agree with Nick about the ability to make cross platform releases (hence withOUT ERTS binaries).

Happy new year