Packaging Erlang libs and apps for a GNU/Linux distribution

[Hartmut Goebel]

Am 12.07.20 um 02:02 schrieb Michael Truog:
> 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.

Having a strong Python background, I'm aware of this.

> Then using rebar3 with ERL_LIBS or rebar2 with the 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 {excl_archive_filters, [".*"]} when building the
> release (if you are using reltool) to avoid stuff getting zipped up
> together.

Thanks, this sounds like the way I'm seeking. I will try this (may take
some time, though)

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@REDACTED               |
| www.crazy-compilers.com | compilers which you thought are impossible |

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20200713/707d396c/attachment.htm>