From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, guix-devel@gnu.org
Subject: Re: guix pack file enumerator?
Date: Mon, 07 Dec 2020 16:14:32 +0100 [thread overview]
Message-ID: <867dpt7inb.fsf@gmail.com> (raw)
In-Reply-To: <875z5f6z1a.fsf@elephly.net>
Hi Ricardo,
On Sun, 06 Dec 2020 at 10:53, Ricardo Wurmus <rekado@elephly.net> wrote:
> What do you think about adding an output format that is no format at all
> but a file enumeration printed to stdout? That way I could use “guix
> pack” to produce a list of files to transfer and use that to transfer
> only the unchanged files. Alternatively, perhaps we could have a
> “directory” format that merely copies (or links) the files to a new
> directory root.
Well, I am not sure if it fits your use case but I am still annoyed to
find the “profile/manifest“ path when I use:
guix pack -f docker --save-provenance -m manifest.scm
then extracts this “profile/manifest” needs:
--8<---------------cut here---------------start------------->8---
docker export -o foo.tar <ID>
tar -xf foo.tar $(tar -tf foo.tar | grep ’profile/manifest’)
--8<---------------cut here---------------end--------------->8---
in order to rebuild an approximation of ’manifest.scm+channels.scm’ if it
has been lost, for example to be able to re-run at anytime:
--8<---------------cut here---------------start------------->8---
docker load < $(guix time-machine -C channels.scm \
-- pack -f docker \
-m manifest.scm)
docker run -ti <TAG>
--8<---------------cut here---------------end--------------->8---
For reference, see <https://yhetil.org/guix/86sgb9nt4k.fsf@gmail.com>.
Therefore, I do not know if this output format is helping for this.
Thanks,
simon
next prev parent reply other threads:[~2020-12-07 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 9:53 guix pack file enumerator? Ricardo Wurmus
2020-12-06 19:33 ` Ryan Prior
2020-12-07 15:14 ` zimoun [this message]
2020-12-08 11:13 ` Ludovic Courtès
2020-12-09 11:04 ` Ricardo Wurmus
2020-12-14 9:48 ` Ludovic Courtès
2020-12-15 2:43 ` Ryan Prior
2020-12-15 9:53 ` Nicolò Balzarotti
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=867dpt7inb.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.