From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id eGquHiBVz2KMrwAAbAwnHQ (envelope-from ) for ; Thu, 14 Jul 2022 01:28:32 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id IO1wHSBVz2LYeQAAG6o9tA (envelope-from ) for ; Thu, 14 Jul 2022 01:28:32 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 3D4653A1AA for ; Thu, 14 Jul 2022 01:28:32 +0200 (CEST) Received: from localhost ([::1]:60364 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oBlmR-0002Er-BV for larch@yhetil.org; Wed, 13 Jul 2022 19:28:31 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:37104) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oBllo-0001y3-TC for guix-devel@gnu.org; Wed, 13 Jul 2022 19:27:52 -0400 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]:37809) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oBlll-0002wq-MB for guix-devel@gnu.org; Wed, 13 Jul 2022 19:27:52 -0400 Received: by mail-ej1-x634.google.com with SMTP id os14so431361ejb.4 for ; Wed, 13 Jul 2022 16:27:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sweatshoppe-org.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7wv/CvdZXr7kEadVoxQBlDb48j8cI71WlpVjqlCwZDQ=; b=xPlrZEl1/eD/VTtAC13WMy/E/FDQpBl/08Lqn6wUHURBwae+62DucuFoEmz0wyvU/X s9PbKbddByx+Opkf/8I2cJotIBhocED1kzJjibAJgAF7qPhZIOWNvEKT5JFYMkaLYAiT fhWZJ581Y/vkaaWeRscSMqlWdwpTgkpdr+BmqgY1zVkUU/2PqIggTt199YlkpulhZ275 oderBZR3S9k3WvyeWYBvPa0OOmyBmU1Uf/N+GwKGRQl8yiVYi23JBRR1kZPIhR8HZcWv gtW3+IzG+YIABPeAarzleFD/5eeiiMp5dEHMEw9gABnAbNvDYJfmxyb4zpFKOTB98QVH nytA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7wv/CvdZXr7kEadVoxQBlDb48j8cI71WlpVjqlCwZDQ=; b=hqh7rQMsE6H+k2twPWlIHqtDrMao0Px9F8DnXaqDK53sUaV33DbCiNmQGAD2DKSjsA k/AIZ6nBYoocEYiummMLgnphpwBjGh7hfYak+1IJMIEMrpXQ7U1rYnF+SAfq4PTgjAjx Kv2+c9Jp2m9519V4IHnJmUSajWCEn5lGsaMgiqe1oDxEKNYlgp27/GOLwnaL7/cgDUas YlqtLyTOsOd9/GucD9tfqYal++lP+9XdNxSRVAmPcG8zSu79M8wykRPvJcXb1JaIapo8 OJou9PcCEsTXG9S8CFYoQsk4ViZCgcKM8slkSH73TUHGuD+YTbM6nupp9F0yhT0O+we2 3G5Q== X-Gm-Message-State: AJIora9z0/t8oTO5ABmBK/5DdQbrj4vN7WbKsOEVR5h6+vxtKVJveuJf lM5H+wkm72zYURDF3vjz2m12Q4xn2mEA1Ca1qmGOYg== X-Google-Smtp-Source: AGRyM1u2uQwE2xxuYy9RWugkvDP95EAKNoOKRmhA6sxBfPUlfB9aHMO0N1HdzXuJI1DEBFuuy1aPYipdHUdbmcegh0g= X-Received: by 2002:a17:907:7638:b0:72d:f11b:5ebb with SMTP id jy24-20020a170907763800b0072df11b5ebbmr3386316ejc.647.1657754864230; Wed, 13 Jul 2022 16:27:44 -0700 (PDT) MIME-Version: 1.0 References: <87tu7llpj0.fsf@dominicm.dev> In-Reply-To: <87tu7llpj0.fsf@dominicm.dev> From: Blake Shaw Date: Wed, 13 Jul 2022 23:27:32 +0000 Message-ID: Subject: Re: [WIP Patch] Adding an FHS container to guix shell To: dom@dominicm.dev Cc: John Kehayias , Guix Devel Content-Type: multipart/alternative; boundary="000000000000cebf0905e3b821e7" Received-SPF: none client-ip=2a00:1450:4864:20::634; envelope-from=blake@sweatshoppe.org; helo=mail-ej1-x634.google.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" Authentication-Results: aspmx1.migadu.com; none X-Migadu-Scanner: scn0.migadu.com X-TUID: 16/CZNmMEfRx --000000000000cebf0905e3b821e7 Content-Type: text/plain; charset="UTF-8" hi John! I think it sounds like a swell addition to Guix, something that I would definitely reach for time to time. good stuff. ez, b On Wed, Jul 13, 2022 at 2:26 AM Dominic Martinez wrote: > > John Kehayias writes: > > > First, I wanted to ask how people feel about such a feature. Obviously, > one use > > is to run pre-built binaries (isolated!), but this is also handy for > setting up > > development environments when not able (or wanting) to with Guix > packages only. > > For example, using the rustup [0] scripts, pretty much anything JS, or > just > > following typical Readme instructions to try out something new before > packaging. > > I won't debate the details here other than to say this topic comes up > with Guix > > and I think it is yet another useful tool for guix shell and containers. > > Absolutely! I usually have to resort to Docker containers when building > something that doesn't support GuixSD, so being able to work with them > through Guix would be amazing. > > > What about other uses for this container, like providing an isolated > environment > > to build and run software we can't do fully with bootstrap and sources > (like > > JS)? Could this become some stop-gap to allow people to work with these > > ecosystems in a more controlled way within Guix? Or an alternative build > > environment? Not entirely sure what this could mean, just thinking out > loud. > > I think an interesting idea would be to allow packages to transparently > run in the FHS container (i.e. a shim that turns 'x' into 'guix shell > --fhs-container x -- x'). That way software incompatible with GuixSD in > a way too difficult to patch could be still be packaged and used > transparently, albeit with a significant performance cost. > > Even if packages in Guix proper don't use it, it could be useful for > third-party channels or end-users to whip up packages. > > Thanks so much for this; I've been thinking about getting around to this > feature for quite a while. > --000000000000cebf0905e3b821e7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
hi John!

I think it sounds l= ike a swell addition to Guix, something that I would definitely reach for t= ime to time.

good stuff.

= ez,
b

On Wed, Jul 13, 2022 at 2:26 AM Dominic Martinez &= lt;dom@dominicm.dev> wrote:
<= /div>

John Kehayias <john.kehayias@protonmail.com> writes:

> First, I wanted to ask how people feel about such a feature. Obviously= , one use
> is to run pre-built binaries (isolated!), but this is also handy for s= etting up
> development environments when not able (or wanting) to with Guix packa= ges only.
> For example, using the rustup [0] scripts, pretty much anything JS, or= just
> following typical Readme instructions to try out something new before = packaging.
> I won't debate the details here other than to say this topic comes= up with Guix
> and I think it is yet another useful tool for guix shell and container= s.

Absolutely! I usually have to resort to Docker containers when building
something that doesn't support GuixSD, so being able to work with them<= br> through Guix would be amazing.

> What about other uses for this container, like providing an isolated e= nvironment
> to build and run software we can't do fully with bootstrap and sou= rces (like
> JS)? Could this become some stop-gap to allow people to work with thes= e
> ecosystems in a more controlled way within Guix? Or an alternative bui= ld
> environment? Not entirely sure what this could mean, just thinking out= loud.

I think an interesting idea would be to allow packages to transparently
run in the FHS container (i.e. a shim that turns 'x' into 'guix= shell
--fhs-container x -- x'). That way software incompatible with GuixSD in=
a way too difficult to patch could be still be packaged and used
transparently, albeit with a significant performance cost.

Even if packages in Guix proper don't use it, it could be useful for third-party channels or end-users to whip up packages.

Thanks so much for this; I've been thinking about getting around to thi= s
feature for quite a while.
--000000000000cebf0905e3b821e7--