From: John Kehayias <john.kehayias@protonmail.com>
To: Dominic Martinez <dom@dominicm.dev>
Cc: guix-devel@gnu.org
Subject: Re: [WIP Patch] Adding an FHS container to guix shell
Date: Fri, 15 Jul 2022 15:44:56 +0000 [thread overview]
Message-ID: <4ZllqzHVVS2lCT94KwCw7gv4ltIhfGsH3m_A2LrSf3D08y5NtEbQpYopJoBpT4NPGziNEj57Ng-FpvHNg4Odzr30xYZmbpPNcSBvbJkyqa4=@protonmail.com> (raw)
In-Reply-To: <87tu7llpj0.fsf@dominicm.dev>
Hi Dominic,
------- Original Message -------
On Tuesday, July 12th, 2022 at 10:11 PM, Dominic Martinez wrote:
>
>
>
> John Kehayias john.kehayias@protonmail.com writes:
>
> > 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.
>
Yes, this is something I was thinking of, as a partial stop-gap for when you need to use software that can't be fully packaged the way we want for Guix. Not sure what the details would look like exactly (internally), but could be a useful tool to have.
> Thanks so much for this; I've been thinking about getting around to this
> feature for quite a while.
You are welcome and thanks for the kind words! I've also been thinking about this for a while, and luckily a lot of this was laid out in what others have done (and myself for non-free packaging).
I'm already using a variation of this to do some development work that otherwise wouldn't be possible without maybe a VM or using another machine.
John
next prev parent reply other threads:[~2022-07-15 15:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 15:59 [WIP Patch] Adding an FHS container to guix shell John Kehayias
2022-07-12 17:34 ` Vagrant Cascadian
2022-07-15 15:41 ` John Kehayias
2022-07-13 2:11 ` Dominic Martinez
2022-07-13 23:27 ` Blake Shaw
2022-07-15 15:44 ` John Kehayias [this message]
2022-07-14 10:01 ` zimoun
2022-07-15 15:46 ` John Kehayias
2022-07-14 14:59 ` Liliana Marie Prikler
2022-07-15 16:00 ` John Kehayias
2022-07-15 13:43 ` Maxim Cournoyer
2022-07-15 16:35 ` John Kehayias
2022-07-15 13:45 ` Maxim Cournoyer
2022-07-18 11:40 ` Ludovic Courtès
2022-07-20 21:22 ` John Kehayias
2022-07-20 23:49 ` Maxime Devos
2022-07-21 3:15 ` John Kehayias
2022-07-21 0:20 ` debbugs irritation Was: " Csepp
2022-07-21 4:18 ` John Kehayias
2022-07-21 16:45 ` zimoun
2022-07-21 20:22 ` Csepp
2022-08-18 10:55 ` zimoun
2022-08-19 22:13 ` jbranso
2022-07-21 4:25 ` John Kehayias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='4ZllqzHVVS2lCT94KwCw7gv4ltIhfGsH3m_A2LrSf3D08y5NtEbQpYopJoBpT4NPGziNEj57Ng-FpvHNg4Odzr30xYZmbpPNcSBvbJkyqa4=@protonmail.com' \
--to=john.kehayias@protonmail.com \
--cc=dom@dominicm.dev \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).