| 15 Dec 2024 |
 LilleCarl (Salsa9) | I'm gonna power wash the machine and see if that helps | 19:09:53 |
| LilleCarl (Salsa9) | But it's the same as running NixOS on a RPI with a shitty SD card, it'll die sooner than later | 19:10:20 |
 markuskowa | You mean, because you download a nixpkga tarball too often? | 19:10:27 |
| LilleCarl (Salsa9) | No the local git repo | 19:10:38 |
| LilleCarl (Salsa9) | ~/Code/nixos | 19:10:42 |
| markuskowa | Ah, ok I see. | 19:10:53 |
| LilleCarl (Salsa9) | But it might be the filesystem metadata blocks that get broken, I don't really know | 19:11:24 |
| LilleCarl (Salsa9) | They'll be written quite a lot with nixos/home-manager in general 😄 | 19:11:56 |
| markuskowa | But this is always the case, when you use "src = ./.", even without flakes. | 19:12:20 |
| LilleCarl (Salsa9) | Yeap, and they're still not implemented like gnu coreutils cp | 19:13:01 |
| LilleCarl (Salsa9) | If they were reflink copied on filesystems that support it, it would be so much lighter on block devices | 19:13:30 |
| LilleCarl (Salsa9) | (XFS, btrfs, bcachefs and friends would then just make a reflink and CoW if it's ever written to, but since it's a RO fs it's never written to so CoW only happens when you change a file within your repo) | 19:14:21 |
| LilleCarl (Salsa9) | But it's not implemented because it isn't portable to MacOS and every FS etc.... 😥 | 19:14:42 |
| markuskowa | Yes, reliying on fs specific features sounds tricky. | 19:17:41 |
| LilleCarl (Salsa9) | https://github.com/coreutils/coreutils/commit/25725f9d41735d176d73a757430739fb71c7d043 I mean, gnu coreutils does it by default for cp | 19:18:39 |
| markuskowa | Did you check if Lix has attempted to tackle this problem? | 21:00:18 |
| LilleCarl (Salsa9) | I did read the changelog for the 2 Lix releases that's been released so far but there was nothing that I could find. I kinda neglected the problem and spun up a hetzner VM to work through instead | 21:03:33 |
| 16 Dec 2024 |
 Claes | Unfortunately I can't make it this time. Got a cold and many end-of-year things piling up. Need to prioritize those. Hope you have a good time and see you next year instead! | 11:33:49 |
 igorramazanov | Ok, sorry for the late notice, but I secured an office space for us, so we don't have to hang out in to lobby, if we want to | 12:39:13 |
| igorramazanov | The office is in the "A-House" coworking building, near to Rådsmansgatan and Tekniska Högskolan stations, Östermalmsgatan 26A
If we want, then we can gather there | 12:41:39 |
| markuskowa | Sorry to hear. Get well and enjoy the holidays. | 12:50:26 |
| markuskowa | Sounds good to me. I'm fine with either solution. What does the rest think about the location? | 12:51:32 |
| igorramazanov | 
Download 20241216_135628_4381125336594371811.jpg | 12:56:42 |
| igorramazanov | 
Download 20241216_135645_3907664419029472730.jpg | 12:56:52 |
| LilleCarl (Salsa9) | That does look nice | 14:12:10 |
| LilleCarl (Salsa9) | 
Download image.png | 20:12:41 |
| LilleCarl (Salsa9) | Hetzner Cloud VM's local storage is NVMe attached locally. That's 2nd RAM right?! 😆 | 20:13:29 |
| LilleCarl (Salsa9) | A small but convenient thing in both HM and NixOS module systems: | 20:18:12 |
| LilleCarl (Salsa9) | * A small but convenient thing in both HM and NixOS module systems:
You can assign a package you're building like lib.mypkgs.pkg = pkgs.pkg.overrideAttrs()
Then you can reference it under
config.lib.mypkgs.pkg in the module system, or if you wanna nix build
nixosConfigurations.myhost.config.lib.mypkgs.pkg
homeConfigurations.myuser.config.lib.mypkgs.pkg
If you wanna be quick and dirty and can't be bothered to make options and don't need/want to overlay the package in nixpkgs.
| 20:20:46 |
| markuskowa | Alternative: use an overlay and use your on sub attribute set:
self: super: { mypkgs.pkg = pkgs.pkg.override {}; }
| 21:17:23 |
