From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix describe -p and Guix commit?
Date: Tue, 24 Sep 2019 10:05:57 +0200 [thread overview]
Message-ID: <87v9tim84a.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ0TPAa_Scu+2m+hRVh79X9jFZ3rnv7yutGj3UAYgDH-tQ@mail.gmail.com> (zimoun's message of "Fri, 20 Sep 2019 19:08:12 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> How to track from which channel and commit the packages in a profile come from?
Pro tip: open the ‘manifest’ file of the profile, and search for
“provenance”. You’ll see things like:
--8<---------------cut here---------------start------------->8---
("openssl"
"1.1.1d"
"out"
"/gnu/store/4is5a8hy20rkaq4q08vxf1b355vw0fjg-openssl-1.1.1d"
(propagated-inputs ())
(search-paths
(("SSL_CERT_DIR"
("etc/ssl/certs")
#f
directory
#f)
("SSL_CERT_FILE"
("etc/ssl/certs/ca-certificates.crt")
#f
regular
#f)))
(properties
(provenance ;;<- this!
(repository
(version 0)
(url "https://git.savannah.gnu.org/git/guix.git")
(branch "master")
(commit
"18a613fb29bf053b344bca585e78a2cf26b44469")))))
--8<---------------cut here---------------end--------------->8---
It’s an undocumented and unused feature, mostly because I wouldn’t know
how to expose it at the CLI level. Ideas welcome!
> 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
This seems to be a mixture of ‘guix describe’ and ‘guix package -I’,
right? I’m not sure what you’re expecting here.
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-09-24 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 17:08 guix describe -p and Guix commit? zimoun
2019-09-24 8:05 ` Ludovic Courtès [this message]
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=87v9tim84a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).