| 29 Jul 2025 |
emily | (my bad, my own dev env was messed up :P) | 19:05:32 |
raitobezarius | awesome work, thanks emily! | 19:59:09 |
emily | don't test me, I might remove more things from the packaging 😈 | 19:59:48 |
raitobezarius | nix develop --phase testPhase emily | 20:01:42 |
emily | fwiw, I'm happy to re-add the flag for https://gerrit.lix.systems/c/lix/+/3833/5. but since internal-api-docs apparently takes 32 seconds on CI, I think it would only be for closure, not for build speed | 20:02:53 |
emily | and the closures of doxygen and rapidcheck are small | 20:03:47 |
emily | hmmm | 20:14:20 |
emily | I notice that the derivation in Nixpkgs already did this devdoc stuff and I just wasted a non-trivial amount of time :) | 20:14:37 |
emily | is there no systematic sync between those two? | 20:14:44 |
emily | I'll leave what I have up since it's an improvement over HEAD, but it seems like it would be good to minimize the drift between those two to avoid redundant work. | 20:16:09 |
Marie | hi, I do a applyPatches thing to apply PR's to my nixpkgs and I've been getting really annoyed that lix copies nixpkgs into the store on every invocation, even though it is already in the store.
From googling around this seems to be a known issue. If I call my patched thing "source" the problem goes away.
Does anyone know if there is a good reason to only allow "source" here: https://git.lix.systems/lix-project/lix/src/commit/93acdd40f6c3eab1a25ea03d7a160433ed551677/lix/libfetchers/path.cc#L138 | 21:57:17 |
Marie | Seems to work fine when I remove the restriction, but I don't know much about the codebase, so no idea if this could break something | 22:11:36 |
jade_ | i think there is an issue about this somewhere | 23:56:34 |
jade_ | i am not sure lol | 23:56:40 |