unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Brian Cully <bjc@spork.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Patches for elpa-admin
Date: Fri, 15 Apr 2022 15:44:27 +0000	[thread overview]
Message-ID: <877d7q9wro.fsf@posteo.net> (raw)
In-Reply-To: <87lew61ixz.fsf@ditto.jhoto.spork.org> (Brian Cully's message of "Fri, 15 Apr 2022 11:05:53 -0400")

Brian Cully <bjc@spork.org> writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> I have actually been looking into implementing a TRAMP backend that
>>> would tunnel all communication through a Guix shell.  I think in that
>>> case Flymake should be able to make use of that.
>>
>> That sounds nice.  We'd need a solution that can be made to work
>> "everywhere", so the API should be sufficiently generic that it can make
>> use of various sandboxing systems.
>
> 	I would love a system that can handle this in a
> container-agnostic manner. The primary wrinkle I can see right now is
> that while ‘guix shell’ will happily spin up and use an environment from
> scratch, other containers treat those as separate steps (eg, FreeBSD
> jails need to be installed on disk before a ‘jexec’ can be issued in
> them).
>
> 	I suppose, even Guix needs to have a manifest of some sort to
> run ‘guix shell’ against, which is /sort of/ like the install phase of
> jails, if you squint hard enough.

Not necessarily, you can just list the packages you need when starting
the shell

    $ type markdown
    bash: type: markdown: not found
    $ guix shell markdown
    [env] $ which markdown
    markdown is /gnu/store/...

The question is if this requires some separate infrastructure, of if
container support can be supported via TRAMP (e.g. like
https://github.com/emacs-pe/docker-tramp.el does for Docker).

> -bjc

-- 
	Philip Kaludercic



  reply	other threads:[~2022-04-15 15:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  8:40 Patches for elpa-admin Philip Kaludercic
2022-04-15  4:01 ` Stefan Monnier
2022-04-15  7:18   ` Philip Kaludercic
2022-04-15 14:40     ` Stefan Monnier
2022-04-15 15:05       ` Brian Cully
2022-04-15 15:44         ` Philip Kaludercic [this message]
2022-04-15 15:37       ` Philip Kaludercic
2022-05-21 11:38       ` Philip Kaludercic
2022-05-31  8:37         ` Philip Kaludercic

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877d7q9wro.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=bjc@spork.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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/emacs.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).