From: Hilton Chain <hako@ultrarare.space>
To: nils@landt.email
Cc: help-guix@gnu.org
Subject: Re: Recursive substitute-keyword-arguments / setting default on build system
Date: Wed, 27 Sep 2023 22:13:50 +0800 [thread overview]
Message-ID: <87pm23r9ep.wl-hako@ultrarare.space> (raw)
In-Reply-To: <2042058673.297636.1695726486678@office.mailbox.org>
Hi Nils,
On Tue, 26 Sep 2023 19:08:06 +0800,
nils@landt.email wrote:
>
> Hello,
>
> I use a slightly customized emacs package, and want to use it as the package that is used in emacs-build-system for the emacs plugins I'm using.
> The default emacs gets garbage collected and takes quite a while to reinstall, I would like to avoid that. Also, it seems cleaner to build the plugins with the exact version that they will be used with.
>
> Here's what I have:
>
> (define emacs-package
> ((const
> ((options->transformation
> '((with-configure-flag . "emacs=--program-transform-name='s/^ctags$/ctags.emacs/'")))
> emacs))))
>
> (define (set-build-system-emacs plugin-package)
> (package
> (inherit plugin-package)
> (arguments
> (substitute-keyword-arguments (package-arguments plugin-package)
> ((#:emacs emacs) `,emacs-package)))))
>
> (map set-build-system-emacs package-list)
>
> From what I can tell this does work for the packages in package-list, but not for any inputs to those packages. That makes total sense to me, but I don't know how to solve it.
> Any pointers? Or is it possible to set the default package for a build system, removing the need for this mapping altogether?
`package-input-rewriting' (documented in [1]) can be used for the
purpose:
--8<---------------cut here---------------start------------->8---
(map (package-input-rewriting
`((,emacs-minimal . ,emacs-package)
(,emacs . ,emacs-package)))
package-list)
--8<---------------cut here---------------end--------------->8---
Thanks
---
[1]: https://guix.gnu.org/en/manual/devel/en/html_node/Defining-Package-Variants.html
next prev parent reply other threads:[~2023-09-27 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 11:08 Recursive substitute-keyword-arguments / setting default on build system nils
2023-09-27 14:13 ` Hilton Chain [this message]
2023-09-27 17:41 ` nils
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=87pm23r9ep.wl-hako@ultrarare.space \
--to=hako@ultrarare.space \
--cc=help-guix@gnu.org \
--cc=nils@landt.email \
/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.
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).