From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:39593) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iuc7y-0005ST-Pa for gwl-devel@gnu.org; Thu, 23 Jan 2020 08:02:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iuc7x-000514-A1 for gwl-devel@gnu.org; Thu, 23 Jan 2020 08:02:30 -0500 References: <875zh3w3yp.fsf@elephly.net> From: Ricardo Wurmus Subject: Re: How to install GWL? In-reply-to: Date: Thu, 23 Jan 2020 14:02:07 +0100 Message-ID: <87v9p2uy0g.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gwl-devel-bounces+kyle=kyleam.com@gnu.org Sender: "gwl-devel" To: zimoun Cc: gwl-devel@gnu.org zimoun writes: > Hi Roel, > > On Thu, 23 Jan 2020 at 12:16, Roel Janssen wrote: > >> I initially wanted the GWL to be part of Guix, and I think that could >> greatly simplify things. So by installing GWL, you get the "workflow" >> and "process" subcommands that work with the version of Guix returned >> by: >> $ guix --version > > I agree that with the current situation, it is confusing and hard to > know which "guix --version" is used when running "guix workflow". > It is what I tried to describe in my other email to this thread. I believe that by spawning =E2=80=9Cguix repl=E2=80=9D and using it as an i= nferior we can remove the confusion, and we would make the separation of what is library code and what is run-time code clearer. Currently, that=E2=80=99s not what we=E2=80=99re doing. Instead we use Gui= x as a library (whatever version of the =E2=80=9Cguix=E2=80=9D package is availabl= e in the version of Guix used), and *also* use that version to install software. That=E2=80=99s clearly not desirable, hence my email. -- Ricardo