all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: List of installed package, version pairs
Date: Wed, 16 Jan 2019 14:27:40 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1901161352510.30166@marsh.hcoop.net> (raw)
In-Reply-To: <CAE4v=piyV+gHjekp0YmU5ons-Ed6gN6OpR0rpuqiBAoACSHA4A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Wed, 16 Jan 2019, Gábor Boskovits wrote:

> 
> Hello Jack,
> you could also try to make sense of the individual profile generation
> manifests.
> 
> The union of those should give a farily comprehensive list, and it comes with versions.

Yes, this looks pretty good, thanks. I think that this gets me all the 
surface packages exposed in all the profiles. However, I believe that it 
is still missing the packages installed as dependencies.

One thought is to drop back to manipulating store objects. I can get a 
list of references using query-path-info from the guix store module, and 
recurse down those references to build the graph. In the end I have to 
then guess the package names and versions from the store paths.

From my experimentation, it seems that store paths/objects are really what 
Guix works with and is aware of, and not package names and version that 
are reported as what's installed on traditional distributions. Perhaps I 
can convince our security office to be happy with store paths.

Thoughts?
Jack

  reply	other threads:[~2019-01-16 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 22:03 List of installed package, version pairs Jack Hill
2019-01-10  7:33 ` Efraim Flashner
2019-01-15 21:28   ` Jack Hill
2019-01-16  7:35     ` Gábor Boskovits
2019-01-16 19:27       ` Jack Hill [this message]
2019-01-17 11:17         ` Ricardo Wurmus
2019-01-18  8:36 ` Giovanni Biscuolo

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=alpine.DEB.2.20.1901161352510.30166@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=boskovits@gmail.com \
    --cc=help-guix@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.