From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Guix Devel" <guix-devel@gnu.org>
Subject: Re: Identical files across subsequent package revisions
Date: Wed, 23 Dec 2020 11:41:19 +0100 [thread overview]
Message-ID: <86blekst2o.fsf@gmail.com> (raw)
In-Reply-To: <86eejgsu2y.fsf@gmail.com>
Hi again,
Sorry, I have not finished my previous email. Wrong keystroke in the
wrong buffer because misuse of the Ludo’s code. :-)
On Wed, 23 Dec 2020 at 11:19, zimoun <zimon.toutoune@gmail.com> wrote:
>> I wanted to evaluate that by looking at store items corresponding to
>> subsequent revisions of a package (be it different versions or rebuilds
>> induced by dependencies), and this is what the program below does.
What I wanted to illustrate is “revision” does not mean “new version“
and I do not know what is the typical usage by people; aside Guix
dev. :-)
How many times per week or month people are doing “guix pull && guix
upgrade” almost blindly without reviewing what is new?
Last, I was trying to understand what is the “revision” number
corresponding to which outputs. For example r-minimal:
<https://data.guix.gnu.org/repository/1/branch/master/package/r-minimal/output-history>
There are 3 outputs with 4.0.3, so I am expecting 3 similar revisions in
the chart. Then 3 others with 4.0.2, then 2 others with 4.0.1.
In the 6 revisions in the chart, I was trying to figure out what does
mean the ’0’: r-minimal against which other one, i.e., which Guix commit
against which other one. Idem for 1,2,3,4,5. :-)
BTW, really interesting topic! Thanks Ludo. :-)
Cheers,
simon
next prev parent reply other threads:[~2020-12-23 10:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 22:01 Identical files across subsequent package revisions Ludovic Courtès
2020-12-23 9:08 ` Taylan Kammer
2020-12-23 10:50 ` Pierre Neidhardt
2020-12-23 22:06 ` Mark H Weaver
2020-12-23 22:47 ` Jonathan Brielmaier
2020-12-23 23:42 ` Mark H Weaver
2020-12-23 10:19 ` zimoun
2020-12-23 10:41 ` zimoun [this message]
2020-12-27 22:22 ` Ludovic Courtès
2020-12-23 11:48 ` Christopher Baines
2020-12-23 13:10 ` Miguel Ángel Arruga Vivas
2020-12-23 14:07 ` zimoun
2020-12-23 15:40 ` Julien Lepiller
2020-12-23 19:07 ` Miguel Ángel Arruga Vivas
2020-12-27 22:29 ` Ludovic Courtès
2021-01-06 9:39 ` Ludovic Courtès
2020-12-29 20:01 ` pukkamustard
2021-01-06 9:27 ` Ludovic Courtès
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=86blekst2o.fsf@gmail.com \
--to=zimon.toutoune@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).