all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Store channel specification in profile
Date: Tue, 3 Mar 2020 22:49:17 +0100	[thread overview]
Message-ID: <CAJ3okZ2EeVie7F1+s98upVjdrOi5r_3M+xTbN=CS_Fv9Esgb_A@mail.gmail.com> (raw)
In-Reply-To: <87ftf0j6zq.fsf@gnu.org>

Hi Ludo,

On Mon, 24 Feb 2020 at 17:16, Ludovic Courtès <ludo@gnu.org> wrote:

> > ;; Thanks to Ivan Vilata-i-Balaguer for this:
> > (define (guix-commit)
> >   (let ((guix-manifest (profile-manifest (string-append (getenv "HOME") "/.config/guix/current"))))
> >     (match (assq 'source (manifest-entry-properties (car (manifest-entries guix-manifest))))
> >       (('source ('repository ('version 0) _ _
> >                              ('commit commit) _ ...))
> >        commit)
> >       (_ #f))))
> >
> > (match (command-line)
> >   ((_ where)
> >    (format #t ";; commit: ~a\n" (guix-commit))
> >    (pretty-print
> >     `(specifications->manifest
> >       ',(guix-manifest where))))
>
> Emitting channel info as comments like this, and/or a warning when
> there’s a conflict (packages coming from different commits of the same
> channel) could be done as a second step.

The snippet uses the last commit of "guix pull", right?
Or the commit of last installed package with "guix package -i"?

Even if it can be done as a second step, the commits of each installed
packages are IMHO the key point of the exporter. Because otherwise, I
am doing "guix package -I | cut" and I am almost done.

Cheers,
simon

      parent reply	other threads:[~2020-03-03 21:49 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 14:55 Store channel specification in profile Pierre Neidhardt
2019-11-26 16:40 ` Konrad Hinsen
2019-11-26 19:12   ` Pierre Neidhardt
2019-11-26 19:35     ` Konrad Hinsen
2019-12-02 15:58       ` zimoun
2019-12-09 17:11   ` Ludovic Courtès
2019-12-09 17:21     ` Pierre Neidhardt
2019-12-12 19:50       ` zimoun
2019-12-12 22:35         ` Pierre Neidhardt
2019-12-13 12:16           ` zimoun
2019-12-19 16:12             ` Ludovic Courtès
2019-12-19 17:18               ` zimoun
2020-01-06 20:07         ` Pierre Neidhardt
2020-01-06 21:09           ` zimoun
2020-01-08 15:17             ` Pierre Neidhardt
2020-01-08 19:31               ` zimoun
2020-01-11 23:48               ` Ludovic Courtès
2020-01-13 14:02                 ` Pierre Neidhardt
2020-01-13 14:46                   ` zimoun
2020-01-13 14:37                 ` zimoun
2020-01-13 14:59                   ` Pierre Neidhardt
2020-01-13 15:53                     ` zimoun
2020-01-13 16:53                       ` Pierre Neidhardt
2020-01-30 19:24                         ` Pierre Neidhardt
2020-01-31  8:51                           ` zimoun
2020-01-31  9:21                           ` Konrad Hinsen
2020-01-31 11:21                             ` Pierre Neidhardt
2020-01-31 12:15                               ` Pierre Neidhardt
2020-01-31 16:01                                 ` Konrad Hinsen
2020-02-05 11:08                           ` Ludovic Courtès
2020-02-06 10:59                             ` Pierre Neidhardt
2020-02-07 21:28                               ` Ludovic Courtès
2020-02-08 17:09                                 ` Pierre Neidhardt
2020-02-11 14:10                                   ` Ludovic Courtès
2020-02-11 14:18                                     ` Pierre Neidhardt
2020-02-24 16:16                                       ` Ludovic Courtès
2020-02-25 10:32                                         ` Pierre Neidhardt
2020-03-03 21:43                                           ` zimoun
2020-03-04  8:09                                             ` Pierre Neidhardt
2020-03-04 13:24                                               ` zimoun
2020-03-03 21:49                                         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ3okZ2EeVie7F1+s98upVjdrOi5r_3M+xTbN=CS_Fv9Esgb_A@mail.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.