[erlang-questions] Ability to add app directories explicitly for reltool
Thu Jan 12 11:42:27 CET 2012
I'm sorry, my explanation was really messy.
It seems like in that case reltool will *see* and somehow *validate*
all Erlang applications it finds in the "lib" directory, no matter if
they are included into reltool.config or not. Maybe this should be
considered as wrong behavior.
So, in my example erlson wasn't included anywhere in reltool.config.
It just had 'erl_parse' module included into the application. Btw,
apparently Anton has recently removed erl_parse.erl from his
repository, just because it had been causing problems with release
Of course, this error is quite specific, but maybe there are more
possible errors that I just don't know.
On Thu, Jan 12, 2012 at 2:18 PM, Siri Hansen <> wrote:
>> The only possible problem I can see is that any projects that cause
>> conflicts in reltool will make us unable to build release packages for
>> *the rest* of the projects that reside in the same directory.
>> Say, I had erlson in my projects directory, and it was causing the
>> conflicts during release package generation (well, placing
>> erl_parse.erl into application listing is wrong, it definitely needs
>> to be fixed).
>> Probably, the same goes to projects that may contain same modules in
>> the applications listing (rabbitmq and riak_core both use
>> gen_server2.erl, and those modules are actually different; this
>> doesn't affect any of them but definitely but won't let us build
>> release package).
>> Maybe, there are some more rare errors that might occur as well.
> I'm not sure that I understand everything here... Do you mean that with my
> proposal reltool will *see* some applications which it shall not include in
> the release package? And that the fact that some of these applications have
> modules with equal names causes problems when building the release package?
> If so, is it not possible to write a reltool config which specifies which
> apps/modules to use - and by this avoid conflicts? Sorry for the stupid
> questions - I just feel like it would be good to understand the problems
More information about the erlang-questions