[erlang-questions] Ability to add app directories explicitly for reltool

[Dmitry Demeshchuk]

Hi, Siri.

I guess, we are moving away from the main conversation.

Don't you think that it would be good to make reltool do the required
job in a simpler way? The way we are discussing works in most cases,
but it's quite unclear for the people who aren't very familiar with
reltool.

Using the existing functionalities to solve problems is often good,
but if the solution becomes complicated, maybe a new functionality
should be created instead.

On Thu, Jan 12, 2012 at 6:47 PM, Siri Hansen <erlangsiri@REDACTED> wrote:
> Ah... this is interesting... a missing test case maybe - but I'm not sure if
> it is a bug.
>
> What happens is that the duplicated module erl_parse causes erlson to become
> derived since a module with the same name is used by stdlib and several
> other applications. If it was only stdlib, then I guess reltool could make
> the assumption that the module to use is the one in the same application and
> thus never make erlson derived (because to this module, that is). However,
> since the module in this case is also used by other applications, this
> assumption is not that obvious.
>
> The easiest way to get around this right now is to be more specific in the
> config file to make sure that erlson (or only the erl_parse module) is
> excluded... e.g. by adding
>
> {app, erlson, [{incl_cond,exclude}]} or
> {app, erlson, [{mod,erl_parse,[{incl_cond,exclude}]}]}
>
> (The latter would allow erlson to be derived if any of it's other modules
> were used by other applications)
>
> Regards
> /siri
>
> 2012/1/12 Dmitry Demeshchuk <demeshchuk@REDACTED>
>>
>> Try running this gist: https://gist.github.com/1600020
>>
>> reltool.config will reside in lib/gproc/rel/
>>
>> Thank you.
>>
>



-- 
Best regards,
Dmitry Demeshchuk