| 31 Jul 2025 |
 emily | raitobezarius: do you expect buildDirOverride to be used elsewhere in future? it is currently set and consumed only in one function and all the uses/sets are NOPs | 17:39:20 |
 raitobezarius | yeah | 17:39:39 |
| emily | is the idea that it will be set from outside the worker? or only consumed outside of it? | 17:40:11 |
| emily | I am having trouble following the intent | 17:40:16 |
| emily | it's also used inconsistently already | 17:43:12 |
| raitobezarius | In reply to @emilazy:matrix.org
is the idea that it will be set from outside the worker? or only consumed outside of it? It's the idea of having a build context | 18:03:34 |
| raitobezarius | That can be inherited from RPC and so on | 18:03:43 |
 jade_ | it is especially interesting for when you just want flake pinning but have a giant repo and don't care about the exact contents of what is copied into the store in a repo e.g. if you are doing leaf packages or a dev shell or w/e | 18:14:57 |
| jade_ | it reduces the time for every single nix command to run by 10s+ at work | 18:15:15 |
| jade_ | or on nixpkgs | 18:15:18 |
| emily | put up a big stack to fix https://git.lix.systems/lix-project/lix/issues/913 and clean up a bunch of stuff :) | 21:40:27 |
| raitobezarius | thank you! | 21:44:29 |
| raitobezarius | emily can you add the code owneras reviewers with the "suggest owners" button? | 21:45:16 |
| emily | can I uhh | 21:45:38 |
| emily | do that for the whole stack at once? | 21:45:41 |
| emily | or do I have to do it for every single CL | 21:45:44 |
| raitobezarius | let me check | 21:46:36 |
| raitobezarius | yeah no i think you'd need to add it for every CL but we definitely need to look into something to make it easier | 21:47:44 |
| raitobezarius | it's fine, you don't have to do it i will handle this | 21:47:53 |
