From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:44727) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iW3Kf-0000HD-43 for guix-patches@gnu.org; Sat, 16 Nov 2019 14:02:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iW3Kd-0005hl-Of for guix-patches@gnu.org; Sat, 16 Nov 2019 14:02:05 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:59117) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iW3Kd-0005he-Ln for guix-patches@gnu.org; Sat, 16 Nov 2019 14:02:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iW3Kd-0002k7-Hk for guix-patches@gnu.org; Sat, 16 Nov 2019 14:02:03 -0500 Subject: [bug#37912] [PATCH] gnu: elixir: Update to 1.9.2. Resent-Message-ID: Date: Sat, 16 Nov 2019 20:01:16 +0100 (CET) From: Oskar =?UTF-8?Q?K=C3=B6=C3=B6k?= Message-ID: In-Reply-To: <87o8xbwzim.fsf@gnu.org> References: <875zk4plty.fsf@devup.no> <87o8xbwzim.fsf@gnu.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_27770_1245448669.1573930876151" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: 37912 <37912@debbugs.gnu.org> Cc: Marius Bakke ------=_Part_27770_1245448669.1573930876151 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Thanks. I went ahead and did some further reading on the constraints of Eli= xir Releases and in the end it seems the current behaviour is actually just= fine. The documentation itself notes that there is already effectively a dependen= cy on package managers: > In addition to matching the target triple, it is also important that thet= arget has all of the system packages that your application will need atrunt= ime. A common one is the need for OpenSSL when building an applicationthat = uses :crypto or :ssl, which is dynamically linked to ERTS. The othercommon = source for native dependencies like this comes from dependenciescontaining = NIFs (natively-implemented functions) which may expect todynamically link t= o libraries they use. > These system packages are typically managed using the system package mana= ger,but if necessary, you can also bundle the compiled object files in the = release,as long as they were compiled for the same target. This means that if you're creating an Elixir Release with Elixir built in G= uix, you should also have the needed Guix packages installed on your target= . Optionally the user can create a script that modifies the release to be c= ompatible with the target (e.g. replace /gnu/store/* references with /bin/*= ). Oskar Nov 16, 2019, 18:34 by ludo@gnu.org: > Hi Oskar, > > Oskar K=C3=B6=C3=B6k skribis: > > >>From f2eb88f567f93e578e3c2df76046fed4f45645f8 Mon Sep 17 00:00:00 2001 > >> From: =3D?UTF-8?q?Oskar=3D20K=3DC3=3DB6=3DC3=3DB6k?=3D >> Date: Thu, 24 Oct 2019 23:37:38 +0300 >> Subject: [PATCH] gnu: elixir: Update to 1.9.2. >> >> * gnu/packages/elixir.scm (elixir): Update to 1.9.2. >> > > Thanks for the updated patch! I believe this addresses the comments > that Marius made, and it builds fine for me, so I went ahead and applied > it. > > Thank you! > > Ludo=E2=80=99. > ------=_Part_27770_1245448669.1573930876151 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi

Thanks. I went ahead and did some further reading on the constraints of Elixir=20 Releases and in the end it seems the current behaviour is actually just=20 fine.

The docume= ntation itself notes that there is already effectively a dependency on pack= age managers:
> In addition to matching the= target triple, it is also important that the target has all of the system packages that your application will need at runtime. A common one is the need for OpenSSL when building an application that uses :crypto or :ssl, = which is dynamically linked to ERTS. The other common source for native dependencies like this comes from dependencies containing NIFs (natively-implemented functions) which may expect to dynamically link to libraries they use.
> T= hese system packages are typically managed using the system package manager= , but if necessary, you can also bundle the compiled object files in the rele= ase, as long as they were compiled for the same target.

This means that if you're creating an Elixir Release with Elixir built in=20 Guix, you should also have the needed Guix packages installed on your=20 target. Optionally the user can create a script that modifies the=20 release to be compatible with the target (e.g. replace /gnu/store/*=20 references with /bin/*).

Oskar

=

Nov 16, 2019, 18:34 by ludo@gnu.org:
Hi Oska= r,

Oskar K=C3=B6=C3=B6k <oskar@maatriks.ee> s= kribis:

>>From f2eb88f567f93e578e3c2df76046fe= d4f45645f8 Mon Sep 17 00:00:00 2001
From: =3D?UTF-8?q?Oskar=3D20K=3DC3=3DB6=3DC3=3DB6k?= =3D <oskarkook@maatriks.ee>
Date: Thu, 24 Oct 2019 23:37:38 +0300
Subject: [PATCH] gnu: elixir: Update to 1.9.2.

* gnu/packages/elixir.scm (elixir): Update to 1.9.2.
<= /div>

Thanks for the updated patch! I believe t= his addresses the comments
that Marius made, and it builds fine for me, so I went ahead and applied
it.

Thank you!

Ludo=E2=80=99.

------=_Part_27770_1245448669.1573930876151--