[erlang-questions] Bundling C dependencies with a release
Tue Oct 25 16:54:59 CEST 2016
I don't bundle deps in release. I thing all dependencies should be handled
by system packet manager, so you never miss security updates.
I'm creating a *.deb packet for my application with all dependencies
listed. Then I simply install it with this command - 'dpkg -i release.deb
&& apt-get -f install'. If you want, you can create repository for your
application, add it to /etc/apt/sources.list, and install it via 'apt-get
I'm pretty sure you can do similar thing for RH servers as well.
2016-10-25 19:35 GMT+07:00 Radu Popescu <i.radu.popescu@REDACTED>:
> I'm developing an Erlang application which is structured as an OTP
> release. It contains OTP applications and some native executables (written
> in C++). One of the Erlang dependencies also requires libsodium.
> When the time will come to deploy this - mostly to RH and Ubuntu/Debian
> servers, the idea is to have something as self-contained as possible.
> Are there best practices for how to handle C library dependencies for an
> Erlang/OTP release? I appreciate any advice.
> Best regards,
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions