From: Paul Garlick <pgarlick@tourbillion-technology.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: getting started with guix import nix
Date: Wed, 14 Dec 2016 16:53:52 +0000 [thread overview]
Message-ID: <1481734432.3704.18.camel@tourbillion-technology.com> (raw)
In-Reply-To: <87oa0fjt92.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
Thank you, Ludo.
I have:
$ git describe
v0.11.0-3373-g2df3d14
My Nixpkgs directory is not managed by git. It was installed by the Nix install script. It seems to have the same structure as the Github repository:
$ ls /home/paul/.nix-defexpr/channels/nixpkgs
doc maintainers pkgs README.md svn-revision
lib nixos COPYING default.nix
> It may be that we’re not getting the same XML output from
> ‘nix-instantiate’ and that somehow confuses the XML parser in your
> case.
>
> To investigate, you’d need to run the same ‘nix-instantiate’ command
> that snix.scm invokes, same its XML output, and then try parsing it
> with
> ‘xml->sxml’ from (sxml simple).
>
Following the snix.scm code, I have tried:
$ nix-instantiate --strict --eval --xml -A opencascade_oce
/home/paul/.nix-defexpr/channels/nixpkgs
This command sends xml to standard output for a few minutes, before I
kill the process. Is it common for this process to need a long time?
I have noticed in the Nix manual this comment on the --strict option:
Warning: This option can cause non-termination, because lazy
data structures can be infinitely large.
Maybe this is a Nix problem?
Paul.
[-- Attachment #2: Type: text/html, Size: 1749 bytes --]
next prev parent reply other threads:[~2016-12-14 16:54 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 [this message]
2016-12-15 12:33 ` Paul Garlick
2016-12-19 9:43 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1481734432.3704.18.camel@tourbillion-technology.com \
--to=pgarlick@tourbillion-technology.com \
--cc=help-guix@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.