all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, "Frederick M. Muriithi" <fredmanglis@protonmail.com>
Subject: Using Guix archive (Help!)
Date: Wed, 3 Jan 2018 12:08:36 +0100	[thread overview]
Message-ID: <20180103110836.GA15026@thebird.nl> (raw)

Hi,

I am trying to send a NAR archive to Fred. We are facing a few issues.
First I created the archive

   env GUIX_PACKAGE_PATH=../guix-bioinformatics/ ./pre-inst-env guix archive --export -r --no-grafts genenetwork2 > gn2.nar

and Fred installed the key and unpacked it. Unfortunately it does not
contain package dependencies, such as mysql:

   https://gitlab.com/genenetwork/guix-bioinformatics/blob/master/gn/packages/genenetwork.scm#L194

somehow propagated-inputs don't go into the archive. You'd think they are critical
dependencies.

  Q1: is that to be expected? 

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?

and

  Q4: is there a nice way to include a profile path in the store that
      can be used quickly?

The alternative is tarballing an environment/container, but the
problem there is that Fred's Guix daemon won't be aware of the new
packages. We want to avoid using Docker.

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

Thanks! I tried using NAR Files before and gave up. I hope it is clear
why.

Pj.

             reply	other threads:[~2018-01-03 11:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 11:08 Pjotr Prins [this message]
2018-01-06  6:04 ` Using Guix archive (Help!) Pjotr Prins
2018-01-06 12:46 ` Ricardo Wurmus
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180103110836.GA15026@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=fredmanglis@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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.