From: Tobias Geerinckx-Rice <me@tobias.gr>
To: pjotr.public12@thebird.nl
Cc: guix-devel@gnu.org, fredmanglis@protonmail.com
Subject: Re: Using Guix archive (Help!)
Date: Mon, 8 Jan 2018 16:15:52 +0100 [thread overview]
Message-ID: <a1db3766-8b42-8287-3fbf-9dbe6299fc63@tobias.gr> (raw)
In-Reply-To: <20180107103211.GA3362@thebird.nl>
Pjotr,
Pjotr Prins wrote on 07/01/18 at 11:32:
> I have limited internet these weeks, but when I have more space I can
> look at Nix tooling again. See if there is something to view the
> contents of a nar file.
Apparently[0] Nix 1.12 has a new ‘nix’ UI or wrapper with direct support
for listing NAR contents.
It[1] seems to work on modern-day (decompressed) Guix NARs too:
$ curl https://mirror.hydra.gnu.org/guix/nar\
> /gzip/5nhqwkvy7v51jd8lf4krljfbl01v6rx3-e2fsprogs-1.43.6 > my.nar.gz
$ gunzip my.nar.gz
$ /nix/store/*/bin/nix ls-nar -lR my.nar /
dr-xr-xr-x 0 ./bin
-r-xr-xr-x 18216 ./bin/chattr
-r-xr-xr-x 1540 ./bin/compile_et
-r-xr-xr-x 13888 ./bin/lsattr
-r-xr-xr-x 1356 ./bin/mk_cmds
dr-xr-xr-x 0 ./etc
-r--r--r-- 808 ./etc/mke2fs.conf
dr-xr-xr-x 0 ./include
lrwxrwxrwx 0 ./include/com_err.h -> et/com_err.h
dr-xr-xr-x 0 ./include/e2p
[...]
I haven't tried more than the above commands, nor do I use Nix anymore,
nor do I have any idea how good or reusable the code is, but it's a start.
Kind regards,
T G-R
[0]: https://github.com/NixOS/nix/issues/1257
[1]:
https://hydra.nixos.org/build/67181169/download/1/nix-1.12pre5839_6e098968-x86_64-linux.tar.bz2
next prev parent reply other threads:[~2018-01-08 15:13 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
2018-01-07 9:16 ` Pjotr Prins
2018-01-07 10:32 ` Pjotr Prins
2018-01-08 15:15 ` Tobias Geerinckx-Rice [this message]
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=a1db3766-8b42-8287-3fbf-9dbe6299fc63@tobias.gr \
--to=me@tobias.gr \
--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 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.