From: "Tomáš Čech" <sleep_walker@gnu.org>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: 25852@debbugs.gnu.org
Subject: bug#25852: Users not updating their installations of Guix
Date: Sun, 5 Mar 2017 10:43:27 +0100 [thread overview]
Message-ID: <20170305094327.3m67twgmae6nyloq@penguin> (raw)
In-Reply-To: <20170305092511.GA9142@mail.thebird.nl>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
On Sun, Mar 05, 2017 at 09:25:11AM +0000, Pjotr Prins wrote:
>On Sun, Mar 05, 2017 at 08:56:41AM +0100, Tomáš Čech wrote:
>> And IMHO the best and also "Guix way" could be making guix-daemon aware of
>> possible newer versions in /gnu/store and execing them instead...
>
>Giving a loud warning should really be sufficient. The Guix way is to
>have a system not surprise us by shifting the sand under our feet ;)
Yes, but the surprise is made when your expectations are different
from what is naturally expected.
My expectation is that when `guix pull' is run, it should update whole
guix, not just part (guix - guix-daemon).
Surprise is when it does not do it.
Removing the surprise can be either by splitting the package to make
obvious it is independent part or making `guix pull' able to update
guix-daemon as well.
Loud warning is really sufficient for user (or admin) but not for
distribution package maintainer.
Another option is that I will do the split by myself and take
guix-daemon sources from GIT but I'm sure I'll make much worse job
than you.
Best regards,
S_W
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-05 9:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 21:11 bug#25852: Users not updating their installations of Guix Leo Famulari
2017-02-24 5:42 ` Pjotr Prins
2017-03-02 18:16 ` sirgazil
2017-03-04 20:29 ` Tomáš Čech
2017-03-04 22:43 ` Leo Famulari
2017-03-05 7:56 ` Tomáš Čech
2017-03-05 9:25 ` Pjotr Prins
2017-03-05 9:43 ` Tomáš Čech [this message]
2017-03-06 14:52 ` Ricardo Wurmus
2017-03-07 6:54 ` Pjotr Prins
2017-03-06 21:12 ` Ludovic Courtès
2017-03-06 21:34 ` Leo Famulari
2017-03-07 6:33 ` Tomáš Čech
2017-03-07 19:51 ` Leo Famulari
2017-03-07 20:58 ` Tomáš Čech
2017-03-07 22:22 ` Leo Famulari
2017-03-08 6:25 ` Tomáš Čech
2017-03-08 8:45 ` Leo Famulari
2017-03-08 9:24 ` Tomáš Čech
2017-03-08 18:15 ` Leo Famulari
2017-03-09 7:38 ` Efraim Flashner
2017-03-09 10:58 ` Ludovic Courtès
2017-03-09 12:42 ` Tomáš Čech
2017-03-09 15:42 ` Ludovic Courtès
2017-03-07 7:32 ` Mark H Weaver
2017-03-07 10:35 ` Ludovic Courtès
2017-03-11 1:48 ` Mark H Weaver
2017-05-10 13:12 ` Ludovic Courtès
2017-05-10 14:13 ` myglc2
2017-05-10 20:16 ` Ludovic Courtès
2017-05-12 6:06 ` Ricardo Wurmus
2017-05-12 8:29 ` Ludovic Courtès
2017-05-12 17:10 ` myglc2
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=20170305094327.3m67twgmae6nyloq@penguin \
--to=sleep_walker@gnu.org \
--cc=25852@debbugs.gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).