From: Pierre Neidhardt <mail@ambrevar.xyz>
To: George Clemmer <myglc2@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Some general guix questions
Date: Tue, 22 Jan 2019 11:28:57 +0100 [thread overview]
Message-ID: <87y37drno6.fsf@ambrevar.xyz> (raw)
In-Reply-To: <cuca7k9snxd.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
I realized that something was missing from the above manifest generators: the
outputs.
My shot at it:
--8<---------------cut here---------------start------------->8---
(use-modules (guix profiles)
(ice-9 match)
(ice-9 pretty-print))
(match (command-line)
((_ where)
(pretty-print
`(specifications->manifest
',(map (lambda (entry)
(let ((out (manifest-entry-output entry)))
(if (string= out "out")
(manifest-entry-name entry)
(format #f "~a:~a"
(manifest-entry-name entry)
(manifest-entry-output entry)))))
(manifest-entries (profile-manifest where))))))
(_ (error "Please provide the path to a Guix profile.")))
--8<---------------cut here---------------end--------------->8---
Unlike George, I'm not sorting the entry, so the latest package will appear
first in the manifest. I haven't made up my mind yet as to which one is more
useful, sorted or not.
Thoughts?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-01-22 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:43 Some general guix questions Divan Santana
2019-01-08 17:13 ` Pierre Neidhardt
2019-01-08 20:36 ` Ricardo Wurmus
2019-01-08 21:24 ` Pierre Neidhardt
2019-01-08 21:40 ` Ricardo Wurmus
2019-01-09 18:09 ` George Clemmer
2019-01-22 10:28 ` Pierre Neidhardt [this message]
2019-01-09 7:51 ` Divan Santana
2019-01-08 19:26 ` George Clemmer
2019-01-09 7:50 ` Divan Santana
2019-01-08 20:00 ` Tonton
2019-01-09 7:48 ` Divan Santana
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=87y37drno6.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=myglc2@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.
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).