[erlang-questions] relx extended deps

Loïc Hoguin essen@REDACTED
Tue Jan 27 19:02:54 CET 2015

On 01/27/2015 06:48 PM, e@REDACTED wrote:
>> The solution retained is to fix the .app file, and document a way to
>> remove SSL if you don't want it.
> Seems to me rather a workaround than a solution.
> It is acceptable, as well as it is acceptable to "sed" the .app file
> from within the Makefile, but a proper solution must not involve manual
> labour, especially when it is tinkering with a 3rd-party software (what
> is provided as a dep ideally must work without tinkering)
> Also, i want to emphasize, that this problem has an *ALGORITHMIC*
> solution, which automatically moves the problem from the realm of humans
> to the real of computers -- no human should be forced to do algorithmic
> job.

Not my call on any of these things though. OTP team acknowledged the 
need for runtime dependencies but as far as I know there are no solution 
for this today. Similarly, Erlware is aware of it but dismissed making 
applications start ordered.

Traditionally it seems like the solution was to exclude unneeded 
applications from the release when generating it (using the 
reltool.config file), so the retained solution brings nothing new, and 
that's a good thing.

If you are really serious on your solution, then the first step would 
probably to write an EEP, and then submit a patch to OTP with an 
implementation of said EEP for all involved code (reltool, kernel, 
possibly systool also...)

Loïc Hoguin

More information about the erlang-questions mailing list