From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Extending Guix without using the Guile load path
Date: Tue, 08 Dec 2020 12:03:17 +0100 [thread overview]
Message-ID: <87blf4woei.fsf@gnu.org> (raw)
In-Reply-To: <878sab7n2a.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 06 Dec 2020 02:14:37 +0100")
Hi,
Ricardo Wurmus <rekado@elephly.net> skribis:
> Keeping the directory tree of the extension separate from the “guix
> pull” profile would ensure that the core features of Guix keep working,
> no matter how badly broken an extension might be.
Yeah.
> So I’m thinking that we should instead define GUIX_EXTENSIONS_PATH as a
> list of directories containing merely the *entry points* for additional
> Guix commands. For example, the GWL would provide a script “workflow”
> in a directory $prefix/share/guix/extensions/ (or whatever), and that
> script is a wrapped executable that sets its own %load-path and
> %load-compiled-path as needed (and determined at build time). All Guix
> does is search for matching executables on GUIX_EXTENSIONS_PATH when
> asked for an unknown command.
>
> This is disappointingly simple, but I think it’s one of the safest
> things to do.
Yes, sounds like a good idea.
> An incidental side effect of doing things this way is that extensions
> could, in theory, be written in languages other than Guile (stretching
> the meaning of “extension” to its limits).
Oooh, this is eviiiil! :-)
Ludo’.
next prev parent reply other threads:[~2020-12-08 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 15:36 Extending Guix without using the Guile load path Ricardo Wurmus
2020-02-19 19:46 ` Gábor Boskovits
2020-02-19 20:40 ` Julien Lepiller
2020-03-12 13:29 ` Ludovic Courtès
2020-03-17 18:32 ` Joshua Branson
2020-03-17 19:36 ` Julien Lepiller
2020-10-31 22:53 ` Ricardo Wurmus
2020-10-31 22:53 ` Ricardo Wurmus
2020-11-01 22:23 ` Ludovic Courtès
2020-12-06 1:14 ` Ricardo Wurmus
2020-12-08 11:03 ` Ludovic Courtès [this message]
2021-01-05 10:18 ` [PATCH] Discover extensions via GUIX_EXTENSIONS_PATH Ricardo Wurmus
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=87blf4woei.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).