relx does not accept {mod, []} in the config file

[lehoff]

As I read the rel documentation one can either omit the mod key or give it as {mod, []} when there is nothing that has to be started in an application. I could be misreading it.

Currently relx only works when mod is omitted.

[tsloughter]

Are you referring to mod in the .app file?

[lehoff]

Yes I was, but that wasn't clear in the ticket - sorry.

See http://www.erlang.org/doc/man/app.html - the default value for mod is
[].

On 10 September 2013 05:13, Tristan Sloughter notifications@github.comwrote:

Are you referring to mod in the .app file?

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

http://www.linkedin.com/in/torbenhoffmann
@lehoff

[tsloughter]

It is systools that is complaining when mod is not defined, not relx. So that documentation must only be applying to application handling and not systools (like how registered is required for systools use but not otherwise)...

The output I got for an example I had replacing mod with {mod, []}:

Provider (rlx_prv_assembler) failed with: {error,
                                           {rlx_prv_assembler,
                                            {release_script_generation_error,
                                             systools_make,
                                             [{error_reading,
                                               {egit_sshd,
                                                {{missing_param,mod},

So I'm going to close this ticket.