From: Ricardo Wurmus <rekado@elephly.net>
To: George Clemmer <myglc2@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
YOANN P <yoann_mac_donald@hotmail.com>
Subject: Re: ~/.guix-profile/manifest usage with "guix package -m [manifest]" / "guix pack -m [manifest]" etc..
Date: Tue, 02 Oct 2018 22:41:02 +0200 [thread overview]
Message-ID: <87lg7gt735.fsf@elephly.net> (raw)
In-Reply-To: <cuclg7gz3t2.fsf@gmail.com>
Hi George,
> My thinking is that if there was an easy way to produce “manifests as
> passed to ‘guix package -m’” from profiles, it would be a handy: an easy
> way for someone that has gone down the incremental path to switch to
> manifests and an easy way to update one's manifest after incremental
> changes.
Do you mean something like this?
--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 manifest-entry-name (manifest-entries (profile-manifest where))))))
(_ (error "Please provide the path to a Guix profile.")))
--8<---------------cut here---------------end--------------->8---
You can put this in a file “manifest-to-manifest.scm” and run it like
this from a Guix source checkout:
./pre-inst-env guile -s manifest-to-manifest.scm /path/to/.guix-profile > my-manifest.scm
You can then proceed to install the generated manifest with:
guix package -m my-manifest.scm -p /path/to/new/.guix-profile
If that’s what you’re looking for I suppose we could find a place for
something like that under the umbrella of “guix package”.
--
Ricardo
next prev parent reply other threads:[~2018-10-02 20:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 19:55 ~/.guix-profile/manifest usage with "guix package -m [manifest]" / "guix pack -m [manifest]" etc YOANN P
2018-09-26 10:19 ` Ludovic Courtès
2018-09-27 20:03 ` YOANN P
2018-09-27 21:49 ` Alex Kost
2018-09-29 16:33 ` Ludovic Courtès
2018-10-01 20:17 ` George Clemmer
2018-10-01 22:40 ` YOANN P
2018-10-02 12:46 ` Ludovic Courtès
2018-10-02 16:55 ` George Clemmer
2018-10-02 20:41 ` Ricardo Wurmus [this message]
2018-10-02 21:35 ` George Clemmer
2018-10-08 12:26 ` Ludovic Courtès
2018-10-10 14:07 ` George Clemmer
2018-10-11 13:44 ` Ludovic Courtès
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=87lg7gt735.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
--cc=yoann_mac_donald@hotmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).