From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Garlick Subject: Re: getting started with guix import nix Date: Wed, 14 Dec 2016 16:53:52 +0000 Message-ID: <1481734432.3704.18.camel@tourbillion-technology.com> References: <1481632579.2545.11.camel@tourbillion-technology.com> <87oa0fjt92.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=-lICHwSvv41tfvOY0m9kh" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56243) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cHCof-0001IO-BD for help-guix@gnu.org; Wed, 14 Dec 2016 11:54:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cHCoe-0003q9-Ha for help-guix@gnu.org; Wed, 14 Dec 2016 11:54:05 -0500 In-Reply-To: <87oa0fjt92.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ludovic =?ISO-8859-1?Q?Court=E8s?= Cc: help-guix@gnu.org --=-lICHwSvv41tfvOY0m9kh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit 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. --=-lICHwSvv41tfvOY0m9kh Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 8bit

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.

--=-lICHwSvv41tfvOY0m9kh--