From: Maxime Devos <maximedevos@telenet.be>
To: Arun Isaac <arunisaac@systemreboot.net>, Guix Devel <guix-devel@gnu.org>
Subject: Re: Move switch-symlinks to (guix build utils)
Date: Wed, 01 Jun 2022 14:09:14 +0200 [thread overview]
Message-ID: <72a63d9badd632af81adb75b66cd95d9c05bc31a.camel@telenet.be> (raw)
In-Reply-To: <87pmjsdeh7.fsf@systemreboot.net>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
Arun Isaac schreef op wo 01-06-2022 om 13:04 [+0530]:
> Hi Guix,
>
> The switch-symlinks function from (guix utils) is often required in
> activation-service G-expressions. But, only (guix build utils) and not
> (guix utils) is available to such G-expressions. See, for example, the
> pcscd-activation G-expression in (gnu services security-token) where
> switch-symlinks gets
> redefined. https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/services/security-token.scm#n70
>
> Could we move switch-symlinks to (guix build utils)? Would such a change
> require a core-updates cycle?
To avoid a world-rebuild, you could for now make a module (guix build
symlinks) or such? An alternative is (gnu build activation), but then
some (guix ...) modules would depend on (gnu ...).
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-01 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 7:34 Move switch-symlinks to (guix build utils) Arun Isaac
2022-06-01 12:09 ` Maxime Devos [this message]
2022-06-02 15:06 ` Arun Isaac
2022-06-02 15:13 ` Maxime Devos
2022-06-03 16:38 ` Ludovic Courtès
2022-06-03 17:09 ` Maxime Devos
2022-06-03 19:30 ` Ludovic Courtès
2022-06-03 19:30 ` Ludovic Courtès
2022-06-03 23:55 ` bokr
2022-06-04 10:17 ` Maxime Devos
2022-06-06 11:27 ` Arun Isaac
2022-06-06 12:20 ` Maxime Devos
2022-06-08 20:12 ` Arun Isaac
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=72a63d9badd632af81adb75b66cd95d9c05bc31a.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@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 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).