From: Roel Janssen <roel@gnu.org>
To: guix-devel@gnu.org
Subject: Add the git commit id to the generation information
Date: Tue, 30 May 2017 10:00:48 +0200 [thread overview]
Message-ID: <rbuh9026afu.fsf@gnu.org> (raw)
Dear Guix,
I have a feature request.
When I run 'guix pull', install a package, run 'guix pull' again (on
another day), and install another package, I'd get two generations:
> Generation 181 May 22 2017 11:47:37
> + haunt 0.2.1 out /gnu/store/x2bkpzrdbaxavl29r2xg0fip1jjici9q-haunt-0.2.1
>
> Generation 182 May 24 2017 09:52:06 (current)
> + guile-commonmark 0.1 out /gnu/store/k8vq65czfb8k4hvvjvsca34scd9xsxik-guile-commonmark-0.1
Now, if I'd like to go to the Guix packages source code of generation
181, I can only guess at which actual state of the Guix repository this
was, because this timestamp is the timestamp of creating the generation,
not the timestamp of the Guix package state. So, I'd like to propose to
add the commit id to the generation like so:
> Generation 181 May 22 2017 11:47:37 (ae548434337cddf9677a4cd52b9370810b2cc9b6)
> + haunt 0.2.1 out /gnu/store/x2bkpzrdbaxavl29r2xg0fip1jjici9q-haunt-0.2.1
>
> Generation 182 May 24 2017 09:52:06 (current)
> + guile-commonmark 0.1 out /gnu/store/k8vq65czfb8k4hvvjvsca34scd9xsxik-guile-commonmark-0.1
So, 'current' is the one that is installed at that time. Any other
should be traceable through the git commit ID.
This would probably require us to have the repository information
available when building the tarball that will be downloaded by 'guix
pull'. I think this feature is very important because it makes the
generations traceable to the Guix source code, which is needed for
reproducing the same generation.
Is this something we could make? And can we live with the implicit
requirement to have the git repository information available when
building the source tarballs used by 'guix pull'?
Kind regards,
Roel Janssen
next reply other threads:[~2017-05-30 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 8:00 Roel Janssen [this message]
2017-05-30 8:54 ` Add the git commit id to the generation information Ricardo Wurmus
2017-05-30 9:21 ` Roel Janssen
2017-05-30 15:48 ` 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=rbuh9026afu.fsf@gnu.org \
--to=roel@gnu.org \
--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).