From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 36374@debbugs.gnu.org
Subject: bug#36374: ‘guix pull’ should not suggest running ‘guix pull’
Date: Tue, 24 Mar 2020 18:18:17 +0100 [thread overview]
Message-ID: <87bloln02u.fsf@gnu.org> (raw)
In-Reply-To: <87lfxn2vzb.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 27 Jun 2019 11:55:36 +0200")
Ping! :-)
https://issues.guix.gnu.org/issue/36374
Now’s a good time to fix this one!
Ludo’.
Ludovic Courtès <ludo@gnu.org> skribis:
> Hello!
>
> Julien Lepiller <julien@lepiller.eu> skribis:
>
>> Here is a patch to address this issue on Guix System. It creates new
>> files in /etc/skel: an initial profile (.config/guix/initial) tgat
>> only contains a symlink to /run/current-system/profile/bin/guix and
>> the current profile as a symlink to the initial profile.
>>
>> At first boot, and for new users, guix well be found in the current
>> profile, and stays there after guix pull, so we don't need to use hash
>> guix anymore.
>
> I think this addresses the “hash guix” issue (this will no longer be
> needed with this patch), but it only indirectly solves the “guix pull”
> suggestion issue, right?
>
>> From 89b5fa77af87e1a1537c10e929439a902806cc5c Mon Sep 17 00:00:00 2001
>> From: Julien Lepiller <julien@lepiller.eu>
>> Date: Wed, 26 Jun 2019 14:24:55 +0200
>> Subject: [PATCH] gnu: system: Symlink guix inside an initial guix pull
>> profile.
>>
>> This patch adds an initial guix pull profile to the skeletons files used
>> on Guix System. This ensures that users don't have to type 'hash guix'
>> after their first guix pull, and prevents 'guix pull' from suggesting to
>> run 'guix pull' after it finished successfuly.
>
> It prevents the suggestion, but only because the symlink appears to be
> new. If you change the mtime of the symlink, or if you run:
>
> GUIX_DISTRO_AGE_WARNING=1s guix pull
>
> I think you still get the “guix pull” recommendation.
>
>> * gnu/system/shadow.scm (skeleton-directory): Symlink guix inside an
>> initial guix pull profile.
>
> Perhaps we should add it to ‘default-skeletons’ instead of
> special-casing it here? WDYT?
>
> Thanks for working on it!
>
> Ludo’.
next prev parent reply other threads:[~2020-03-24 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 14:08 bug#36374: ‘guix pull’ should not suggest running ‘guix pull’ Ludovic Courtès
2019-06-26 14:19 ` Julien Lepiller
2019-06-27 9:55 ` Ludovic Courtès
2020-03-24 17:18 ` Ludovic Courtès [this message]
2022-03-23 11:23 ` zimoun
2022-03-24 8:37 ` Ludovic Courtès
2022-06-23 9:30 ` zimoun
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=87bloln02u.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36374@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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).