| 31 May 2024 |
 julia | * although I suppose you probably need to do a code review approval again. still not quite used to how gerrit does this / when ok to actualy merge 🙃 | 13:07:20 |
 Qyriad | If the submission button is there, you can merge | 13:11:21 |
| julia | yea ol | 13:13:05 |
| julia | * oki! | 13:13:16 |
|  Ambroisie joined the room. | 13:16:48 |
| julia | welp, nevermind, apparently all the parents in the relation chain have to be done first. which... makes sense, I guess. lol. (i was kinda just amending each individually, though, so 🤷, that relation might be kinda broken now
| 13:23:14 |
| Ambroisie | Yeah, Gerrit is quite naive in its handling of stacked patches
You have to explicitly un-parent independent commits to not have parent-child relationships if you want to be able to merge them out of order | 13:25:24 |
| Qyriad | which you can do with the rebase button, to be clear, but it won't do it automatically | 14:16:46 |
 aprl | hey is there a Lix compile guide somewhere? (we wanna compile it for riscv rn) | 14:31:42 |
 toinux | is MakeFile an accepted answer ? | 15:01:00 |
| toinux | * is "meson.build" an accepted answer ? | 15:01:49 |
| toinux | https://git.lix.systems/lix-project/lix/src/branch/main/doc/manual/src/contributing/hacking.md
everything is detailed here, I was able to create a FreeBSD port by inspiring myself with the following informations | 15:02:17 |
| toinux | btw, is someone willing to implement lix-doc in meson so we can build everything without depending on Nix ?
I already made a quickpatch in FreeBSD ports, but I think something more official would be better | 15:03:12 |
| toinux | * btw, is someone willing to implement lix-doc in meson so we can build everything without depending on Nix ?
I already made a quickpatch in FreeBSD ports, but I think something more official (and present in upstream) would be better | 15:03:28 |
 delroth | https://git.lix.systems/lix-project/lix/issues/256 | 15:05:09 |
| toinux | here is my crappy solution | 15:06:05 |
| toinux | https://github.com/KittenConnect/lix-bsd-port/commit/e9e0861287ebde5b6e7e3ec63b4d36fa74aaa0c1#diff-ff0b79bff742384fb63d206b8c1687f671257abbe5e966d007e5df56283d8f46R9 | 15:06:26 |
| toinux | I'm sure you've got better ideas than this crap
especially "not using cargo in meson" :rofl: | 15:06:57 |
| delroth | (also for some reason all timestamps on git.lix.systems are showing as "now" here - is it just me? my system clock doesn't seem broken | 15:06:59 |
| delroth | * (also for some reason all timestamps on git.lix.systems are showing as "now" here - is it just me? my system clock doesn't seem broken) | 15:07:05 |
 thubrecht | 
Download image.png | 15:07:07 |
| toinux | JavaScript-debugging time | 15:07:29 |
 Lily Foster | In reply to @toinux_net:matrix.org
I'm sure you've got better ideas than this crap
especially "not using cargo in meson" :rofl: i mean there's no workspaces or anything, so you should be able to natively use meson's rust/cargo.toml support | 15:07:59 |
| toinux | In reply to @lily:lily.flowers
i mean there's no workspaces or anything, so you should be able to natively use meson's rust/cargo.toml support I never really used meson more than by patching failing builds, so I don't have any proper implementation ideas | 15:09:03 |
| toinux | just shared the piece of code which unlocked my build, in hope someone else got more experience with meson to implement a proper and persistent solution | 15:09:59 |
| Lily Foster | In reply to @lily:lily.flowers
i mean there's no workspaces or anything, so you should be able to natively use meson's rust/cargo.toml support (idk i remember it being hella spooky though and don't remember details very well) | 15:10:25 |
| delroth | it's not all the timestamps, it's precisely those from a month ago, wtf | 15:11:46 |
| delroth | https://codeberg.org/forgejo/forgejo/issues/2931 | 15:12:15 |
| toinux | https://github.com/github/relative-time-element/issues/281 🚀 | 15:13:12 |
| delroth | thank god for npm /s | 15:14:22 |
