unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: t@fullmeta.me
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Commit of currently installed package?
Date: Tue, 4 Jan 2022 18:42:38 +0100	[thread overview]
Message-ID: <CAJ3okZ0QY_Zsxd5nkXT6MKYhCNmjZQfHd32X3mEOho=DjR7qBg@mail.gmail.com> (raw)
In-Reply-To: <87bl0rjzn8.fsf@fastmail.com>

Hi,

On Tue, 4 Jan 2022 at 17:02, <t@fullmeta.me> wrote:

> At one point I installed emacs-next --with-branch=master. Well,

[...]

> --export-manifest is approximate and doesn't even give package
>   versions. Even if I start playing games with --export-channels
>   or Scheme %current-profile => manifest => lookup in inferior
>   that would still find whatever guix repo commit had for
>   emacs-next, not what I actually have installed.

No, you cannot know.  Well, that information is not stored by Guix,
AFAIK.  Indeed, it could nice, instead of the current "guix package
--export-manifest":

--8<---------------cut here---------------start------------->8---
(use-modules (guix transformations))

(define transform1
  (options->transformation
    '((with-branch . "emacs-next=master"))))

(packages->manifest
  (list (transform1
          (specification->package "emacs-next"))))
--8<---------------cut here---------------end--------------->8---

To replace 'master' by the commit used.

As a workaround, if it is recent enough (not removed by
last-expiry-cleanup ;-)), the temporary Emacs checkout could be still
there. :-)  Give a look at ~/.cache/guix/checkouts/ and probably
5buqmtmwqjycqg4thcbrvijjn74pijwvjy7ueikyoln7r7d7q6kq.


Hope that helps,
simon


      reply	other threads:[~2022-01-04 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 15:12 Commit of currently installed package? t
2022-01-04 17:42 ` zimoun [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='CAJ3okZ0QY_Zsxd5nkXT6MKYhCNmjZQfHd32X3mEOho=DjR7qBg@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=t@fullmeta.me \
    /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.
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).