| 17 Apr 2026 |
 whispers [& it/fae] | the biggest problem to me is that there aren't more structured ways to the tasks that people usually need. like, in this case, everyone has reinvented running pkg-config and then trying to build the library if you have a feature enabled and so you get to gamble on whether it's any good or you have overrides or anything like that | 22:44:48 |
| whispers [& it/fae] | it takes the idea of maximal flexibility (which you're probably right, people would find a way to do given the rest of landscape) and effectively pushes it into the common case so that even normal tasks require this machinery which is inconsistent and resistant to introspection | 22:46:19 |
| whispers [& it/fae] | * it takes the idea of maximal flexibility (which you're probably right, people would find a way to do given the rest of language) and effectively pushes it into the common case so that even normal tasks require this machinery which is inconsistent and resistant to introspection | 22:46:51 |
| whispers [& it/fae] | * it takes the idea of maximal flexibility (which you're probably right, people would find a way to do given the rest of language) and effectively pushes it into the common case so that even normal tasks require this machinery which is ad-hoc, inconsistent, and resistant to introspection | 22:47:08 |
| whispers [& it/fae] | i suspect a lot of it (e.g. this case of library loading) is mostly down to the fact that it's a lot of work to get right and so it was never implemented, but the effects are the same | 22:48:28 |
| whispers [& it/fae] | * | 22:48:56 |
| whispers [& it/fae] | * | 22:49:33 |
 figsoda | something like system-deps built into cargo would definitely be interesting to see | 22:58:21 |
 nim65s | do you think a bazel(-ish) layer would help ? | 23:06:06 |
 emily | unsandboxed proc macros were also a mistake :) | 23:25:05 |
| emily | but tbh cc crate is a worse offender than anything pkg-config-related | 23:25:17 |
| figsoda | agreed | 23:31:47 |
| 18 Apr 2026 |
 Tumble | are you supposed to put Cago.lock in gitignore? | 15:15:49 |
| Tumble | i was thinking of building this for myself
https://github.com/waywallen/waywallen/blob/main/.gitignore
but they gitignored the Cargo.lock file | 15:16:03 |
| Tumble | * are you supposed to put Cargo.lock in gitignore? | 15:16:16 |
 K900 | Generally no | 15:16:23 |
| K900 | Also holy shit is that overengineered | 15:17:33 |
| Tumble | why are most of the things i decide to compile myself, aways have a weird build setup | 15:18:15 |
| Tumble | will i have to generate the lock file seperatly and then slide it into the build proces | 15:20:46 |
| K900 | I mean I would recommend not running that thing at all | 15:21:44 |
| K900 | But that's probably not the answer you're looking for | 15:21:52 |
| K900 | But there are definitely better ways to do whatever the fuck that's doing | 15:22:02 |
| Tumble | i could do that if there were other projects that do the same thing perhaps | 15:23:57 |
| K900 | https://github.com/luisbocanegra/plasma-smart-video-wallpaper-reborn | 15:24:34 |
| 29 Oct 2021 |
|  @grahamc:nixos.org set the history visibility to "world_readable". | 19:57:43 |
| @grahamc:nixos.org changed the room name to "" from "". | 19:57:43 |
| @grahamc:nixos.org changed the room topic to "" from "". | 19:57:43 |
|  Server Stats Discoverer (traveler bot) joined the room. | 19:58:21 |
|  Matrix Traveler (bot) joined the room. | 19:59:14 |
|  Ralith joined the room. | 20:00:28 |
