Generate rebar.lock and few other improvements.

[gleber]

Generating rebar.lock allows to bypass a lot of magical logic in rebar3.

Other improvements described in commit descriptions. Corresponding PR in nixpkgs will follow, but this code will work even without it.

[ericbmerritt]

I am a bit worried about rewriting the rebar.config in place. This works for things we are building, but doesn't really work for development. I wonder if we can't generate a rebar.config.script that does the rewriting on the fly. Or perhaps, its a flag wether we update the rebar.config in place or generate a script.

[gleber]

This part is not new. I believe it was there before.

I've seen some projects which use rebar.config.script on their own, so this
would still be a bit problematic. I think the only way around it is to
either move ask the logic into Nix or provide alternative mode of operation
for development workflow. I wonder if rebar takes an argument which could
point it to a new rewritten configuration file.
On Mar 7, 2016 3:54 PM, "Eric Merritt" [email protected] wrote:

I am a bit worried about rewriting the rebar.config in place. This works
for things we are building, but doesn't really work for development. I
wonder if we can't generate a rebar.config.script that does the rewriting
on the fly. Or perhaps, its a flag wether we update the rebar.config in
place or generate a script.

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

[ericbmerritt]

It looks like we can have a different config by setting the REBAR_CONFIG env variable. That is probably the way to go here.

[ericbmerritt]

@gleber thoughts?

[gleber]

This is a good idea and it looks like the way to go here. I just didn't
have time to try this out yet.
On Mar 11, 2016 00:54, "Eric Merritt" [email protected] wrote:

@gleber https://github.com/gleber thoughts?

—
Reply to this email directly or view it on GitHub
#4 (comment)
.