From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, "Frederick M. Muriithi" <fredmanglis@protonmail.com>
Subject: Re: Using Guix archive (Help!)
Date: Sun, 7 Jan 2018 10:16:24 +0100 [thread overview]
Message-ID: <20180107091624.GA2981@thebird.nl> (raw)
In-Reply-To: <878tdb40kl.fsf@elephly.net>
On Sat, Jan 06, 2018 at 01:46:18PM +0100, Ricardo Wurmus wrote:
> I’m not sure, but it seems wrong. What I used to do is to create a
> profile and export that recursively:
>
> guix archive --export --recursive \
> $(readlink -f /project/.guix-profile) | \
> gzip --stdout - > my-profile.nar.gz
>
> This should include propagated inputs.
I'll try that again, but it does not appear to be so elegant. Besides
an archive is an archive ;). It should be a 'closure'.
> > NAR files are signed. I think it would be very useful to be able to
> > distribute unsigned NAR files.
> >
> > Q2: can signing/checking be made optional?
>
>
>
> > I can't view the contents.
> >
> > Q3: how do we view the contents of a NAR file without unpacking it?
>
> I don’t think you can. It’s a custom format implemented by
> nix/libutil/archive.cc.
Yes, we ought to do something about that. Nix nar files could be be
unpacked before. I'll take a look at that. Not goot to have obscure
formats.
> > Q4: is there a nice way to include a profile path in the store that
> > can be used quickly?
>
> What do you mean by “include … in the store”? With the above command to
> recursively export profiles you get a single archive that can be
> imported to the store as a profile.
It is elegant (if it works) and not elegant at the same time. I am
thinking more of a symlink -S option like we have with pack.
> > Q5: is there an elegant way to add those unpacked store items to the
> > database?
>
> What unpacked store items do you mean?
I mean how to add the contents of a pack image to the store. What
archive does, but then via the pack command.
Well, if archive works properly, pack does not need to do anything ;)
I know pack serves one purpose - deployment without guix - archive
another - deployment with guix. It is that archive is not working so
well, right now. pack could be supporting deployment on guix and
archive could behave a bit more like pack.
I'll take a look at the archive format.
Pj.
next prev parent reply other threads:[~2018-01-07 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 11:08 Using Guix archive (Help!) Pjotr Prins
2018-01-06 6:04 ` Pjotr Prins
2018-01-06 12:46 ` Ricardo Wurmus
2018-01-07 9:16 ` Pjotr Prins [this message]
2018-01-07 10:32 ` Pjotr Prins
2018-01-08 15:15 ` Tobias Geerinckx-Rice
2018-01-08 15:32 ` Pjotr Prins
2018-01-09 12:13 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180107091624.GA2981@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=fredmanglis@protonmail.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.