From: antlers via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
68163@debbugs.gnu.org, david@daviwil.com
Subject: [bug#68163] [PATCH] gnu: Prevent stale cache use when `%package-module-path' is parameterized.
Date: Mon, 08 Jan 2024 23:56:32 +0000 [thread overview]
Message-ID: <c83d9e09-15bc-4bc6-acbc-dd2cf83d266a@app.fastmail.com> (raw)
In-Reply-To: <21937d23-9a81-4090-979d-584f40880a51@app.fastmail.com>
Some final thoughts I had I as I was moving-on:
1.) Mailing list guidelines prob say not to link to Gists, I made sure to include all relevant content in-line and wouldn't have attached them on their own anyways. They're there for the adventurous.
2) No, I don't want to put my packages in a separate channel-- I believe that the average Guix user has one channel for both their configuration and custom packages / services (I don't mean this in a demanding way, clearly happy to scratch my own itches, just anticipating the suggestion).
3.) Yes, my `extract-emacs-packages' parser really does support command-line transformation options and comments in use-package `:guix` blocks-- that snippet is verbatim.
4.) cc davie, he might get a kick outta that snippet
5.) I started preparing the reduced example as a `guix repl' session until I realized it has to be a real file for `module-filename' and `fold-packages' to work-- it could expose a module search-path, but I don't *think* there's a real use-case for that :p
next prev parent reply other threads:[~2024-01-08 23:58 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
2024-01-08 23:04 ` antlers via Guix-patches via
2024-01-08 23:56 ` antlers via Guix-patches via [this message]
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=c83d9e09-15bc-4bc6-acbc-dd2cf83d266a@app.fastmail.com \
--to=guix-patches@gnu.org \
--cc=68163@debbugs.gnu.org \
--cc=antlers@illucid.net \
--cc=david@daviwil.com \
--cc=ludo@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 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.