unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Paul Garlick <pgarlick@tourbillion-technology.com>
Cc: help-guix@gnu.org
Subject: Re: getting started with guix import nix
Date: Mon, 19 Dec 2016 10:43:50 +0100	[thread overview]
Message-ID: <87mvfs8d9l.fsf@gnu.org> (raw)
In-Reply-To: <1481805189.2840.16.camel@tourbillion-technology.com> (Paul Garlick's message of "Thu, 15 Dec 2016 12:33:09 +0000")

Hi!

Paul Garlick <pgarlick@tourbillion-technology.com> skribis:

> I have noticed that the non-termination problem is not confined to the
> opencascage_oce package. If I try 
>
> $ nix-instantiate --strict --eval --xml -A guile
> /home/paul/.nix-defexpr/channels/nixpkgs
>
> that does not terminate either.

Does it just take long, or does it simply not terminate?

I get:

--8<---------------cut here---------------start------------->8---
$ time NIX_REMOTE=daemon nix-instantiate -A guile /data/src/nixpkgs --strict --eval --xml | wc -c
trace: lib.zip is deprecated, use lib.zipAttrsWith instead
trace: `mkStrict' is obsolete; use `mkOverride 0' instead.
trace: `types.list' is deprecated; use `types.listOf' instead
7786158

real	0m0.668s
user	0m0.348s
sys	0m0.160s
$ (cd /data/src/nixpkgs/; git describe)
release-16.03-start-8750-gdde259d
$ nix-instantiate --version
nix-instantiate (Nix) 1.11.2
--8<---------------cut here---------------end--------------->8---

As you can see it produces 7 MiB of XML data, but that’s pretty fast.

HTH,
Ludo’.

  reply	other threads:[~2016-12-19  9:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 12:36 getting started with guix import nix Paul Garlick
2016-12-13 23:37 ` Ludovic Courtès
2016-12-14 16:53   ` Paul Garlick
2016-12-15 12:33   ` Paul Garlick
2016-12-19  9:43     ` Ludovic Courtès [this message]
2016-12-19 16:08       ` Paul Garlick
2016-12-19 20:56         ` 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=87mvfs8d9l.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=pgarlick@tourbillion-technology.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.
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).