unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org, "Frederick M. Muriithi" <fredmanglis@protonmail.com>
Subject: Re: Using Guix archive (Help!)
Date: Sat, 06 Jan 2018 13:46:18 +0100	[thread overview]
Message-ID: <878tdb40kl.fsf@elephly.net> (raw)
In-Reply-To: <20180103110836.GA15026@thebird.nl>


Hi Pjotr,

> somehow propagated-inputs don't go into the archive. You'd think they are critical
> dependencies.
>
>   Q1: is that to be expected?

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.

> 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.

>   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.

>   Q5: is there an elegant way to add those unpacked store items to the
>   database?

What unpacked store items do you mean?

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  parent reply	other threads:[~2018-01-06 12:46 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 [this message]
2018-01-07  9:16   ` Pjotr Prins
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

  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=878tdb40kl.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=fredmanglis@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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).