From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: guix describe -p and Guix commit?
Date: Fri, 20 Sep 2019 19:08:12 +0200 [thread overview]
Message-ID: <CAJ3okZ0TPAa_Scu+2m+hRVh79X9jFZ3rnv7yutGj3UAYgDH-tQ@mail.gmail.com> (raw)
Dear,
How to track from which channel and commit the packages in a profile come from?
For example, today (time T) I run:
guix package -i emacs guile -p my-env
And I forgot to store the result of "guix describe".
Months later, and after several "guix pull" and not changing the
profile "my-env", I would like to reproduce this exact profile on
another machine.
It is easy to extract the version of Emacs and Guile:
guix describe -p my-env
So I can dig in the git history to find the commit introducing the
specific version of Emacs and Guile. Well it is not convenient. :-)
but doable. Then, I run:
guix pull --commit=<hash>
guix package -i emacs guile -p my-new-env
It is also possible to extract the hashes in the store, reading the
file my-env/manifest and my-new-env/manifest.
And they are not the same. The Guix version that I just pulled should
be anterior to the one at time T. Because maybe something in the
dependencies of Emacs or Guile has changed.
Well, I can list all the pulls with "guix pull" and then guess some
commit. But it is not convenient, neither.
What I would expect is:
guix describe -p my-env
Generation 5 Sep 20 2019 17:21:30
emacs 26.2 asdf12
guile 2.2.4 z56qwe
(for example, I updated only Emacs once, 3 times Guile)
What do you think?
Do it make sense?
All the best,
simon
All the best,
simon
next reply other threads:[~2019-09-20 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 17:08 zimoun [this message]
2019-09-24 8:05 ` guix describe -p and Guix commit? Ludovic Courtès
2019-09-24 16:00 ` zimoun
2019-09-28 21:08 ` 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=CAJ3okZ0TPAa_Scu+2m+hRVh79X9jFZ3rnv7yutGj3UAYgDH-tQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--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).