unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Thu, 02 Jun 2022 17:13:15 +0200	[thread overview]
Message-ID: <b1d13140748592bc8c718a0ee4c013f69110d56b.camel@telenet.be> (raw)
In-Reply-To: <87ee07cdfn.fsf@systemreboot.net>

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

Arun Isaac schreef op do 02-06-2022 om 20:36 [+0530]:
> Hi Maxime,
> 
> > 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 ...).
> 
> I don't really mind waiting for the next core-updates cycle. This
> problem has been around for a long time. It wouldn't hurt much to wait a
> bit longer. If there is consensus on this change, I can send a
> patch. WDYT?

Downside of (guix build utils): it makes it harder to modify switch-
symlinks.  I don't know if that's too much of a downside in practice. 
Also, there is a bug in switch-symlinks:

(use-modules (guix utils))
;; simulate an interrupted switch-symlinks (C-c, power interruption, ...)
(symlink "target" "link.new")
;; now try again
(switch-symlinks "link" "target")

ice-9/boot-9.scm:1685:16: In procedure raise-exception:
In procedure symlink: Bestand bestaat al: "link.new"

If we move it to (guix build utils), I'd prefer the bug to be addressed first.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-06-02 15:14 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
2022-06-02 15:06   ` Arun Isaac
2022-06-02 15:13     ` Maxime Devos [this message]
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=b1d13140748592bc8c718a0ee4c013f69110d56b.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).