| 27 Jul 2025 |
 Qyriad | Oh I see what you mean now | 11:54:40 |
| Qyriad | that's a good question then, I'm not suredon' | 11:54:51 |
| Qyriad | * that's a good question then, I'm not sure | 11:54:56 |
 Puna | i think I submitted a theoretical fix for the POWER names? not super familiar with the gerrit workflow yet.
if host_cpu is supposed to be used there, should i make that a separate changelist thingy? | 12:33:39 |
|  kookie joined the room. | 13:40:00 |
 raitobezarius | In reply to @aloisw:julia0815.de
I think we specifically started copying it to prevent this from causing trouble? do you remember which commit / which thing introduced that? | 14:27:51 |
| raitobezarius | moved back to the non optimized version in https://gerrit.lix.systems/c/lix/+/3765/4?tab=comments | 14:27:56 |
| raitobezarius | and added a CL for the optimization | 14:28:00 |
| raitobezarius | with a FIXME for defending against UDS attacks | 14:28:04 |
 aloisw | https://git.lix.systems/lix-project/lix/commit/cf756fdf3c1a804af726703a12ed2990ad6c2639 | 14:30:02 |
| aloisw | According to the commit message here the motivation was avoiding broken symlinks, but the linked commit doing the same for resolv.conf also cites changing file. | 14:30:54 |
 emily | I feel like the store thing would achieve a comparable optimization across platforms while solving any UDS / file changing / etc. worries (but I should stop saying this because I suspect there is complexity to arranging the store copy that i'm just missing :) ) | 15:32:07 |
| emily | copying all the time sounds great to me if Linux has to do it too though :P | 15:32:24 |
| emily | how do you select a range of lines to comment on in Gerrit? | 15:58:20 |
| emily | I feel like I forget and have to remember how every time | 15:58:28 |
| emily | ah you select in the code rather than the gutter | 15:58:37 |
| raitobezarius | In reply to @emilazy:matrix.org
copying all the time sounds great to me if Linux has to do it too though :P i mean, the optimization is dangerous for now :D | 16:01:33 |
| raitobezarius | In reply to @aloisw:julia0815.de
According to the commit message here the motivation was avoiding broken symlinks, but the linked commit doing the same for resolv.conf also cites changing file. with my current proposal, bindPath would follow the symlink I believe | 16:02:37 |
| raitobezarius | so broken symlinks would surface as an exception and break the setup | 16:02:44 |
| raitobezarius | bindPath(source symlink, target, {.followSymlinks = true}) degrades to copyFile(source, target, {.followSymlinks = true}) actually | 16:03:12 |
| raitobezarius | (with the createDirs in addition on the base dir) | 16:03:18 |
| raitobezarius | but ok for the changing files | 16:03:38 |
| raitobezarius | K900 explain yourself | 16:03:41 |
| raitobezarius | did you notice files changing on the fly or not mid-builds? | 16:03:49 |
| raitobezarius | emily fwiw, i'm redoing the testing stuff | 16:04:10 |
 K900 | What | 16:04:22 |
| raitobezarius | i'm going to split into a sandboxed-ca.sh and unsandboxed-ca.sh test suite | 16:04:22 |
| emily | because of issues with Darwin sandbox testing? | 16:04:36 |
| raitobezarius | In reply to @k900:0upti.me
What https://git.lix.systems/lix-project/lix/commit/b469c6509ba616da6df8a27e4ccb205a877c66c9 | 16:04:36 |
| raitobezarius | In reply to @emilazy:matrix.org
because of issues with Darwin sandbox testing? because there's no such thing as building in a diverted store with Darwin | 16:04:49 |
