<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 03/08/2020 06:03, Richard O'Keefe
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABcYAdLsKbzqhG4aBybfdGpU_2FOO5roD1CY=t0wSUTC9+15XQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:monospace,monospace">"Any C program can be
compiled statically ..."</div>
<div class="gmail_default"
style="font-family:monospace,monospace">Would that it were
so. However,</div>
<div class="gmail_default"
style="font-family:monospace,monospace">- you have to have
statically linkable versions of<br>
</div>
<div class="gmail_default"
style="font-family:monospace,monospace"> all the libraries
you depend one, but you might</div>
<div class="gmail_default"
style="font-family:monospace,monospace"> have been given only
.so files</div>
<div class="gmail_default"
style="font-family:monospace,monospace">- the operating system
has to be willing to run</div>
<div class="gmail_default"
style="font-family:monospace,monospace"> statically linked
programs. My preferred operating</div>
<div class="gmail_default"
style="font-family:monospace,monospace"> system stopped
shifting libc.a and the like years</div>
<div class="gmail_default"
style="font-family:monospace,monospace"> ago, which annoyed
me greatly at the time.</div>
<div class="gmail_default"
style="font-family:monospace,monospace"><br>
</div>
<div class="gmail_default"
style="font-family:monospace,monospace">One way to package
everything up so that it appears to</div>
<div class="gmail_default"
style="font-family:monospace,monospace">someone installing it
as a single file and you are</div>
<div class="gmail_default"
style="font-family:monospace,monospace">protected to some
extent from clashes whether your</div>
<div class="gmail_default"
style="font-family:monospace,monospace">dependencies and
others' is to use a container image.</div>
<div class="gmail_default"
style="font-family:monospace,monospace">I know, bloat upon
bloat. Feh!</div>
</div>
<br>
</blockquote>
<p>Unfortunately containers don't solve all the world's problems.
Firstly, they depend on Linux kernel, secondly, they require
docker or an alternative as a dependency when installing. An
Erlang release has the ability to be portable without docker, e.g.
easily moved across similar systems without depending on third
party solutions.</p>
<p>I am essentially looking for a way of deploying an Erlang release
to a system that doesn't have Erlang installed (and doesn't
support docker).</p>
<p>GrzegorzJ<br>
</p>
</body>
</html>