unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Vong <alexvong1995@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Needs enhancement: "is my guix current?"
Date: Tue, 12 Dec 2017 23:55:07 +0800	[thread overview]
Message-ID: <87o9n4q6uc.fsf@gmail.com> (raw)
In-Reply-To: <877etsqf7q.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 12 Dec 2017 13:54:17 +0100")

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

Hello,

I think I've confused things a bit. Well, 'guix refresh' updates package
definitions to match the latest upstream version, but we are the
upstream, so it is not useful here.

I think even if 'guix pull' is being run, the guix installed should
always be newer than the guix known to guix, right?

It is due to how release is done and how 'guix pull' works.

When releasing, a commit X is declared as a release. The release tarball
then contains commit X. The next commit Y changes the snapshot of the
guix known to guix from some old value to X. But the release tarball
still contains the old value since it uses commit X! So if you installed
from a release tarball and have not run 'guix pull' yet, the guix
installed should be newer than the guix known to guix.

Similarly, when running 'guix pull', say master is at commit X, and the
snapshot of the guix known to guix inside that commit X is at commit
Y. Then the guix installed is updated to commit X and the guix known to
guix is updated to commit Y.

Now we observe that commit X is always newer than commit Y. It is
because when you update snapshot, you change the snapshot to the current
commit and then commit. After that, the commit of the snapshot is
already 1 commit behind that of the new current commit! So after you run
'guix pull', the guix installed should be newer than the guix known to
guix.

As a result, the guix installed should always be newer than the guix
known to guix. Is my reasoning valid?

ludo@gnu.org (Ludovic Courtès) writes:

> Hi,
>
> Alex Vong <alexvong1995@gmail.com> skribis:
>
>> I think if you never run 'guix refresh', then the guix installed should
>> always be newer than the guix known to guix.
>
> I think you mean ‘guix pull’, in which case I agree.
>
> (‘guix refresh’ is more of a developer tool: it simplifies updating
> package definitions.)
>
> Ludo’.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2017-12-12 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 12:20 Needs enhancement: "is my guix current?" Hartmut Goebel
2017-12-11 13:23 ` Ludovic Courtès
2017-12-12 10:56 ` Alex Vong
2017-12-12 12:54   ` Ludovic Courtès
2017-12-12 15:55     ` Alex Vong [this message]

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=87o9n4q6uc.fsf@gmail.com \
    --to=alexvong1995@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).