all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: antlers <antlers@illucid.net>
Cc: dev@jpoiret.xyz, 68163@debbugs.gnu.org, zimon.toutoune@gmail.com,
	othacehe@gnu.org, me@tobias.gr, rekado@elephly.net,
	guix@cbaines.net
Subject: [bug#68163] [PATCH] gnu: Prevent stale cache use when `%package-module-path' is parameterized.
Date: Mon, 08 Jan 2024 18:06:02 +0100	[thread overview]
Message-ID: <87a5pf4ux1.fsf@gnu.org> (raw)
In-Reply-To: <b2aaf81a7ae81d47ff5091cb4012764124c6f61c.1704002781.git.antlers@illucid.net> (antlers@illucid.net's message of "Sun, 31 Dec 2023 06:06:21 +0000")

Hi,

antlers <antlers@illucid.net> skribis:

> * gnu/packages.scm(find-package-by-name/direct): Convert `delay'-ed cache
> construction in closure into a form memoized over `%package-module-path'.
>
> Change-Id: I6e4b4b3fa58082b79aacf307468aec43ec60bf22
> ---
> This enables `specification->package' to be parameterized to resolve packages
> from within the module-under-compilation.
>
> I use this to parse my init.el[0] into packages in my guix-home profile, all
> in one repo.

Looks like you forgot reference [0].

(I’m not sure I understand the use case but seeing your code will surely
help!)

Thanks,
Ludo’.




  reply	other threads:[~2024-01-08 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31  6:06 [bug#68163] [PATCH] gnu: Prevent stale cache use when `%package-module-path' is parameterized antlers via Guix-patches via
2024-01-08 17:06 ` Ludovic Courtès [this message]
2024-01-08 23:04   ` antlers via Guix-patches via
2024-01-08 23:56     ` antlers via Guix-patches via
2024-01-11 18:24 ` Simon Tournier
2024-01-13  0:23   ` antlers via Guix-patches via
2024-01-13  4:41     ` antlers via Guix-patches via
2024-01-17  8:32       ` antlers via Guix-patches via

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=87a5pf4ux1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=68163@debbugs.gnu.org \
    --cc=antlers@illucid.net \
    --cc=dev@jpoiret.xyz \
    --cc=guix@cbaines.net \
    --cc=me@tobias.gr \
    --cc=othacehe@gnu.org \
    --cc=rekado@elephly.net \
    --cc=zimon.toutoune@gmail.com \
    /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.