| 30 Jun 2022 |
 fufexan | this is weird | 11:12:17 |
| fufexan | https://github.com/fufexan/visionfive-nix this is all I've changed | 11:15:55 |
|  nospaces joined the room. | 21:29:59 |
| 1 Jul 2022 |
|  Burrito (marius) changed their profile picture. | 08:27:40 |
| fufexan | In reply to @fufexan:matrix.org
or I guess I could make a global alias in bash/zsh so that alias did not work, will have to think of a different way to make it work | 10:08:11 |
| fufexan | In reply to @fufexan:matrix.org
› nixos-rebuild switch --flake .#visionfive-cross-x86 --target-host nixos@10.0.0.104
warning: Git tree '/home/mihai/Documents/code/git/visionfive-nix' is dirty
/nix/store/rcy3nb3vx7z3dm3lqpwkygph38f3c0rp-nixos-rebuild/bin/nixos-rebuild: line 374: /nix/store/mskilnkr76pjiwhr0wbl1p41pld7bkrc-coreutils-riscv64-unknown-linux-gnu-9.0/bin/mktemp: cannot execute binary file: Exec format error
also fixed this by enabling riscv64 binfmt on my machine | 10:08:32 |
| 5 Jul 2022 |
 luizribeiro | in case any of you are interested, I’ve been collecting all my riscv64 patches on this repo: https://github.com/luizribeiro/nixpkgs-riscv
there’s a bunch of stuff I’ve had to do to get my usual setup to run on the visionfive. stuff like getting llvm to build, building a go bootstrap compiler for riscv64 (they don’t provide one), etc.
I’m putting up PRs but it will take a while for all of it to get upstreamed | 02:15:13 |
| luizribeiro | (it’s obviously based on the awesome work by others who have put up PRs to get the visionfive to boot, of course :) all I’m doing is getting the packages I couldn’t build fixed) | 02:15:53 |
| 6 Jul 2022 |
|  dudeofawesome joined the room. | 06:22:49 |
| 8 Jul 2022 |
|  linear joined the room. | 00:33:25 |
| Burrito (marius) changed their display name from marius851000 to Burrito (Marius). | 15:21:18 |
| Burrito (marius) changed their display name from Burrito (Marius) to Burrito (marius). | 15:24:03 |
 matthewcroughan - nix.how | Alyssa Ross: based on what you were saying about nixos-hardware, does this mean we should be building and caching nixos-hardware? | 17:10:24 |
| matthewcroughan - nix.how | that's the only way I can fathom getting rid of vendor kernels from nixpkgs | 17:10:35 |
 Alyssa Ross | Yeah I think that's a great idea | 17:10:47 |
| matthewcroughan - nix.how | cache.nixos.org would then be able to build and redistribute all vendor kernels from nixos-hardware | 17:11:02 |
| matthewcroughan - nix.how | I think what you're saying about vendor kernels might be premature though | 17:11:24 |
| Alyssa Ross | There are a lot of improvements somebody who wanted to put the effort in could make to nixos-hardware, and that's definitely a big one | 17:11:24 |
| matthewcroughan - nix.how | the reason is because flakes aren't stable yet, and this functionality all relies upon flakes | 17:11:33 |
| Alyssa Ross | no it doesn't | 17:11:38 |
| Alyssa Ross | I've been using nixos-hardware since before flakes existed | 17:11:51 |
| matthewcroughan - nix.how | in practice, nixos-hardware is a flake without legacyPackages | 17:11:51 |
| matthewcroughan - nix.how | it's definitely dependent on flakes as functionality | 17:11:57 |
| matthewcroughan - nix.how | I'm not saying this cannot be expressed without flakes, nor should it, but something to keep in mind | 17:12:08 |
| Alyssa Ross | I don't understand at all the point you're trying to make | 17:12:24 |
| matthewcroughan - nix.how | how people will ultimately use this stuff will be as a flake, since nixos-hardware doesn't have any flake-compat | 17:12:57 |
| Alyssa Ross | you can use nixos-hardware just fine using any of the mechanisms you'd use to evaluate nix code | 17:13:01 |
| Alyssa Ross | I personally use a git subtree | 17:13:06 |
| Alyssa Ross | you could also use niv | 17:13:09 |
| Alyssa Ross | or a channel | 17:13:15 |
