 | DevOS | 31 Members |
| Seeking help and geeking out together on https://github.com/divnix/devos & https://github.com/divnix/digga | 10 Servers |
| DevOS | 31 Members |
| Seeking help and geeking out together on https://github.com/divnix/devos & https://github.com/divnix/digga | 10 Servers |
| Sender | Message | Time |
|---|---|---|
| 4 Dec 2021 | ||
 @gytis-ivaskevicius:matrix.org | https://github.com/NixOS/nix/pull/5577 | 06:02:53 |
| @gytis-ivaskevicius:matrix.org | poggers | 06:02:56 |
 David Arnold (blaggacao) |
| 20:28:11 |
| David Arnold (blaggacao) | ^ would have been my comment, if I could. | 20:28:35 |
| David Arnold (blaggacao) | * ^^ would have been my comment, if I could. | 20:28:42 |
| David Arnold (blaggacao) | Gytis Ivaskevicius: maybe you remembered when I tried some in fup once. These had been quite bit cleaner had there been right associativity. | 20:29:32 |
| David Arnold (blaggacao) | * Gytis Ivaskevicius: maybe you remember when I tried some in FUp once. These had been quite bit cleaner had there been right associativity. | 20:29:59 |
| David Arnold (blaggacao) | * Gytis Ivaskevicius: maybe you remember when I tried some in FUP once. These had been quite bit cleaner had there been right associativity. | 20:30:04 |
| 7 Dec 2021 | ||
 @kraftnix:matrix.org | hey all, is anyone having issues with the latest not sure if I explained that well, basically since updating from | 19:23:58 |
| @kraftnix:matrix.org | I also suddenly have three different flake-utils in my lockfile as well, i tend to make all my flake inputs use the same inputs as each other to reduce the size of my closures (particularly for nixpkgs, but I like to do it for all), and this latest updates has introduced a lot of duplicates where I haven't had any for months | 19:27:34 |
| @kraftnix:matrix.org | so the only way I managed to workaround and get my as well as changing all other follows that use | 19:49:59 |
| @kraftnix:matrix.org | * so the only way I managed to workaround and get my as well as changing all other follows that use | 19:50:23 |
| 9 Dec 2021 | ||
 @cw:kernelpanic.cafe | https://github.com/divnix/devos/blob/main/flake.nix has a bit that refers to what is that core and where is it defined? | 02:19:40 |
| @cw:kernelpanic.cafe | Answering: https://github.com/divnix/devos/blob/287cb82d1ccd74693ae844869baa34228f143c21/profiles/core/default.nix | 02:21:01 |
| @cw:kernelpanic.cafe | I try to enter my user is defined in | 06:21:51 |
 @danielphan.2003:matrix.org | Have you staged users/cw/default.nix in git? | 06:45:36 |
| @cw:kernelpanic.cafe | no! | 07:22:42 |
| @cw:kernelpanic.cafe | staging didn't help | 07:25:58 |
| @cw:kernelpanic.cafe | Oddly though, the cw user change wasn't staged | 07:26:24 |
| @cw:kernelpanic.cafe | * Oddly though, the cw user change wasn't staged either | 07:26:41 |
| @cw:kernelpanic.cafe | In reply to @cw:kernelpanic.cafeNot intended to be bitchy, lol | 08:20:42 |
| David Arnold (blaggacao) | In reply to @kraftnix:matrix.org At work I learned that the follows inputs are not completely gone and that the only really effective way is to reduce & push to the leave:
| 14:27:48 |
| David Arnold (blaggacao) | I also may add, that even if it is a "horrible beast" indeed, it's also more transparent and locally reasonable. The latter is a huge win in complexity reduction. | 14:29:18 |
| David Arnold (blaggacao) | * I also may add, that even if it is a "horrible beast" indeed, it's also more transparent and locally reasonable. The latter is a huge win in complexity containment. | 14:29:46 |
| David Arnold (blaggacao) | At this point, my current best advice to reduce closure size is to fare with a balanced approch: deduplicate the core blobs like nixpkgs and make sure you don't have largely duplicated dep trees, but don't care too much about leaf packages with only a few runtime deps & don't care at all about pure nix libraries. | 14:37:25 |
| David Arnold (blaggacao) | Especially for the latter, the pain of hidden side effects due to incompatibilities between version is also a lot bigger than the gain in closure size reduction or cleanup of the lock file: for example, at one point flake-utils introduced aarch64-darwin and some packages wheren't ready & that broke downstream CIs. | 14:39:25 |
| David Arnold (blaggacao) | * Especially for the latter, the pain of hidden side effects due to incompatibilities between version is also a lot bigger than the gain in closure size reduction or cleanup of the lock file: for example, at one point flake-utils introduced `aarch64-darwin` as a default system and some packages wheren't ready & that broke downstream CIs. | 14:40:04 |
| David Arnold (blaggacao) | * Especially for the latter, the pain of hidden side effects due to incompatibilities between version is also a lot bigger than the gain in closure size reduction or cleanup of the lock file: for example, at one point flake-utils introduced `aarch64-darwin` as a default system and some packages wheren't ready & that broke downstream CIs, because flake checks started failing. | 14:40:35 |
| David Arnold (blaggacao) | * Especially for the latter, the pain of hidden side effects due to incompatibilities between version is also a lot bigger than the gain in closure size reduction or cleanup of the lock file: for example, at one point flake-utils introduced `aarch64-darwin` as a default system and some packages wheren't ready & that broke downstream CIs, because flake checks started failing, iirc. | 14:40:43 |
| David Arnold (blaggacao) | * At work I learned that the issues with follows inputs are not completely gone and that the only _really_ effective way is to reduce & push to the leave: - reduce -> don't bother about non-nixpkgs, since they are usually libs, are small and don't have huge deps themselves - push to the leaf: make it a responsability of the end user flake. (Almost) all follows issues that I still hace seen with recent versions could be resolve when the follows statements are used at the leaf. | 14:41:02 |