[erlang-questions] reltool in R14B03 strange behavior

[Damian Dobroczyński]

Ok. There's no problem. My fault. I've had "excl_app_filter" patterns
which did the job and in fact excluded a bunch of applications from the
release.

-- D.

W dniu 21.06.2011 11:10, Damian Dobroczyński pisze:
> Hi list!
> 
> I'm trying to generate a release with such reltool.config contents:
> 
> {sys, [
>        {lib_dirs, ["../..", "../deps"]},
>        {rel, "mfinder", "1",
>         [
>          kernel,
>          stdlib,
>          sasl,
>          mfinder
>         ]},
>        {rel, "start_clean", "",
>         [
>          kernel,
>          stdlib
>         ]},
>        {boot_rel, "mfinder"},
>        {profile, embedded},
>        {excl_sys_filters, ["^bin/.*",
>                            "^erts.*/bin/(dialyzer|typer)"]},
>        {mod_cond, all},
>        {app_file, all},
>        {excl_archive_filters, [".*"]},
>        {debug_info, strip},
>        {app, stdlib, [{incl_cond, include}]},
>        {app, sasl, [{incl_cond, include}]},
>        {app, kernel, [{incl_cond, include}]}
>       ]}.
> 
> and the result is that the release does not have "inet*" modules beams.
> So, any attempt to run a node of this release ends up with error
> rreporting undefined inet_db:start_link/1 function. What's happening?
> 
> -- D.
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x0CAE3AEB.asc
Type: application/pgp-keys
Size: 5351 bytes
Desc: not available
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110621/2a7d5ba6/attachment.bin>