From mboxrd@z Thu Jan 1 00:00:00 1970 References: <875zh3w3yp.fsf@elephly.net> <8736c755xf.fsf@kyleam.com> From: Ricardo Wurmus Subject: Re: How to install GWL? In-reply-to: <8736c755xf.fsf@kyleam.com> Date: Thu, 23 Jan 2020 11:06:32 +0100 Message-ID: <87y2tyv653.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: Kyle Meyer Cc: gwl-devel@gnu.org List-ID: Kyle Meyer writes: > Hi Ricardo, > > Ricardo Wurmus writes: > >> How should the GWL be installed for maximum convenience and >> compatibility? Does it make sense to install it as a channel so that it >> is tied to the user=E2=80=99s current version of Guix? That would be pr= etty >> awkward and less convenient than just typing =E2=80=9Cguix install gwl= =E2=80=9D. >> >> If we stick with installing the workflow language as a package, how >> should package installation be handled? Should all workflows require a >> channels definition for reproducibility, so that we could instantiate an >> inferior Guix using the exact specified version? If none is provided we >> could fall back to the latest version of Guix. >> >> How does that sound? > > The last combination sounds good to me: support/encourage specifying the > channel definition in the workflow, and fall back to the latest version > of Guix. Though perhaps it'd be better to fall back to the user's > current version instead? My thinking is that the user's version would > be a less frequently moving target, be more likely to have higher > substitute availability, and would more closely match any debugging and > testing the user is doing with, say, `guix environment'. Yes, I agree. I suppose we could achieve this by simply spawning =E2=80=9C= guix repl=E2=80=9D and rely on the environment to give us the user=E2=80=99s cur= rent version of Guix. Then we connect to the spawned REPL. --=20 Ricardo