From: Jack Hill <jackhill@jackhill.us>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: help-guix@gnu.org
Subject: Re: List of installed package, version pairs
Date: Tue, 15 Jan 2019 16:28:42 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.1901151612300.30166@marsh.hcoop.net> (raw)
In-Reply-To: <20190110073328.GE18849@macbook41>
Thanks! I'm still not quite there, but the suggestion below have been
quite helpful in my thinking and experimentation.
On Thu, 10 Jan 2019, Efraim Flashner wrote:
> For packages you have installed in your profile
> 'guix package -I | cut -f1,2 --output-delimiter=@ | sort -u' gives a
> nice list. Perhaps someone else has an idea for the list from your
> os-config.
I think I have an answer for the OS config: pass the --profile option to
guix package, so the guix package command becomes 'guix package
--profile=/var/guix/profiles/system/profile -I'
> Although the code above doesn't take into account build inputs and
> packages that are in your binaries' paths. For that my two initial ideas
> are 'guix package -I | cut -f1 | sort -u | xargs guix size' or
> 'guix package -I | cut -f1 | sort -u | guix refresh --list-transitive'
> and some more shell scripting to get the package and version.
Yes, I did want to inputs in the list as well. However, I worry that
calculating these by passing package names to the current guix may
inadvertently list newer inputs than were used by the, potentially older,
guix that instantiated the profile.
Best,
Jack
next prev parent reply other threads:[~2019-01-15 21:29 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 [this message]
2019-01-16 7:35 ` Gábor Boskovits
2019-01-16 19:27 ` Jack Hill
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.1901151612300.30166@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=efraim@flashner.co.il \
--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.