all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "(" <paren@disroot.org>
Cc: 57317-done@debbugs.gnu.org
Subject: bug#57317: [PATCH 0/2] Implicitly set GUIX_EXTENSIONS_PATH in profiles.
Date: Wed, 7 Sep 2022 11:46:00 +0300	[thread overview]
Message-ID: <YxhaSAtT8L/V4veW@3900XT> (raw)
In-Reply-To: <20220821131222.12411-1-paren@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]

On Sun, Aug 21, 2022 at 02:12:22PM +0100, ( via Guix-patches via wrote:
> Hi Guix!
> 
> This patchset allows Guix to automatically find extensions installed
> in profiles. There's probably a more elegant way to do this, but this
> is the simplest and easiest way I can think of.
> 
> ( (2):
>   build: profiles: Always set GUIX_EXTENSIONS_PATH.
>   gnu: package-management: Remove mentions of GUIX_EXTENSIONS_PATH.
> 
>  gnu/packages/package-management.scm | 11 +----------
>  guix/build/profiles.scm             |  4 ++++
>  2 files changed, 5 insertions(+), 10 deletions(-)
> 

I pushed the first patch from the second set to always set
GUIX_EXTENSIONS_PATH and the second patch from the first set, which only
modifies guix-modules but not the guix package itself. I'm pretty sure
that Guix still needs the search path for the extensions.

As a side note, should something be added to guix shell/environment  so
it finds the extensions too?

Thanks for the patches! Now it should be easier to add extensions.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2022-09-07  8:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21 13:12 [bug#57317] [PATCH 0/2] Implicitly set GUIX_EXTENSIONS_PATH in profiles ( via Guix-patches via
2022-08-21 13:16 ` [bug#57317] [PATCH 1/2] build: profiles: Always set GUIX_EXTENSIONS_PATH ( via Guix-patches via
2022-08-21 13:16   ` [bug#57317] [PATCH 2/2] gnu: package-management: Remove mentions of GUIX_EXTENSIONS_PATH ( via Guix-patches via
2022-08-21 15:43 ` [bug#57317] [PATCH v2 1/2] build: profiles: Implicitly set GUIX_EXTENSIONS_PATH ( via Guix-patches via
2022-08-21 15:43   ` [bug#57317] [PATCH v2 2/2] gnu: package-management: Remove mentions of GUIX_EXTENSIONS_PATH ( via Guix-patches via
2022-08-21 19:38   ` [bug#57317] [PATCH v2 1/2] build: profiles: Implicitly set GUIX_EXTENSIONS_PATH Maxime Devos
2022-08-21 19:41 ` [bug#57317] [PATCH 0/2] Implicitly set GUIX_EXTENSIONS_PATH in profiles Ricardo Wurmus
2022-08-22  9:20   ` Efraim Flashner
2022-09-07  8:46 ` Efraim Flashner [this message]

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

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

  git send-email \
    --in-reply-to=YxhaSAtT8L/V4veW@3900XT \
    --to=efraim@flashner.co.il \
    --cc=57317-done@debbugs.gnu.org \
    --cc=paren@disroot.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.