<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Am 12.07.20 um 02:02 schrieb Michael
Truog:<br>
</div>
<blockquote type="cite"
cite="mid:0c9c2bff-30a4-3e5b-517f-673fb1bf3547@gmail.com"> Do not
install packages into the $OTP_ROOT/lib directory because you get
conflicting dependencies when you go down that path. You should
keep your Erlang applications separate, whether they are in a
release or separate from a release.</blockquote>
<p>Having a strong Python background, I'm aware of this.<br>
</p>
<blockquote type="cite"
cite="mid:0c9c2bff-30a4-3e5b-517f-673fb1bf3547@gmail.com">Then
using rebar3 with ERL_LIBS or rebar2 with the <span class="pl-c1">lib_dirs
configuration set will pull in the dependencies. If you want a
release to have dependencies that may be reused from the local
filesystem, then use </span>{<span class="pl-c1">excl_archive_filters</span>,
[<span class="pl-s"><span class="pl-pds">"</span>.*<span
class="pl-pds">"</span></span>]} when building the release (if
you are using reltool) to avoid stuff getting zipped up together.</blockquote>
<p>Thanks, this sounds like the way I'm seeking. I will try this
(may take some time, though)<br>
</p>
<pre class="moz-signature" cols="72">--
Regards
Hartmut Goebel
| Hartmut Goebel | <a class="moz-txt-link-abbreviated" href="mailto:h.goebel@crazy-compilers.com">h.goebel@crazy-compilers.com</a> |
| <a class="moz-txt-link-abbreviated" href="http://www.crazy-compilers.com">www.crazy-compilers.com</a> | compilers which you thought are impossible |
</pre>
</body>
</html>