Sender | Message | Time |
---|---|---|
11 Jul 2023 | ||
then that default.nix file could be used for reproducibility purposes | 10:14:18 | |
got it | 22:13:55 | |
12 Jul 2023 | ||
08:46:24 | ||
So I've started playing with Nix. I am trying to build an environment with R and some packages installed (inside Docker, just to avoid interfering with my system). Here is the default.nix that I'm using:
| 12:19:26 | |
I can drop into a nix shell using CMD nix-shell /home/renv/default.nix in the Dockerfile and then running a container | 12:20:01 | |
but when I try to build the environment first, and then drop into bash that doesn't work. So when I do
| 12:20:39 | |
* but when I try to build the environment first, and then drop into bash that doesn't work. So when I do
| 12:20:48 | |
* but when I try to build the environment first, and then drop into bash that doesn't work. So when I do
I get following error message
| 12:21:37 | |
surely I'm missing something obvious, but can't find it 😅 | 12:23:01 | |
* but when I try to build the environment first, and then drop into bash that doesn't work. So when I do
I get following error message
| 12:23:29 | |
ok so some more googling led me to write this default.nix:
| 13:04:26 | |
* ok so some more googling led me to write this default.nix:
| 13:04:47 | |
and now it builds successfully | 13:05:00 | |
I guess the issue was that before I wasn't creating an environment, because I wasn't using mkShell explicitely? | 13:05:51 | |
In reply to @brodriguesco:matrix.orgThese general nix questions are better in #nix:nixos.org, but to answer your questions derivations have to produce all outputs, of which out is mandatory. Your expression above did not create the output path expected so your got an error when you tried to build it. mkShell is a wrapper around mkDerivation that simply dumps some text into the output path (see pkgs/build-support/mkShell/default.nix ). | 23:23:44 | |
13 Jul 2023 | ||
Ah great many thanks. I figured it had to do something with the fact that mkShell likely provided the required outputs, which I would have had to provide by hand otherwise | 07:52:14 | |
I've joined the NixOS channel, I'll ask these types of questions in there in the future, thanks! | 07:52:56 | |
17 Jul 2023 | ||
14:29:47 | ||
ok, it's been a while since i looked at this, but i'm having a go at implementing a nix-flakes buildpack for repo2docker which will allow use of a git repo with a flake.nix on https://mybinder.org/ | 14:32:09 | |
story so far is that i got it working 2 years ago using the existing nix buildpack and edolstra's flake-compat, and to prove the long-term reproducibility of nix, it still builds and runs using repo2docker ! https://codeberg.org/jezcope/binder-nix-flakes | 14:34:22 | |
hmm, OK, first roadblock to doing anything with a reasonably recent nixpkgs is this: repo2docker does not work with jupyter-server v2 https://github.com/jupyter-server/jupyter_server/issues/1038 | 16:24:45 | |
is there a standard way to install an old version of a python package? equivalent to pip install jupyter-server<2.0.0 | 16:25:54 | |
I guess I should ask in #python:nixos.org | 16:28:22 | |
18 Jul 2023 | ||
11:06:32 | ||
20 Jul 2023 | ||
hi again, I wrote two blog posts on Nix and R, maybe you’ll find them interesting :) any feedback welcome! | 14:40:00 | |
https://www.brodrigues.co/blog/2023-07-13-nix_for_r_part1/ | 14:40:02 | |
https://www.brodrigues.co/blog/2023-07-19-nix_for_r_part2/ | 14:40:10 | |
In reply to @petrichor:envs.netchecking out an older nixpkgs | 16:12:18 | |
or not using nixpkgs | 16:12:26 | |
fellow Nixers, I'm a beginner and started a series of blog posts that might interest some of you. It focuses on R but I believe a lot of what I describe could be used for any language | 16:19:15 |