| 16 Oct 2023 |
 pwychowaniec | * hi, do we have any procedure for deprecating nix-community projects? 👀
(or at least changing status to looking for maintainer) | 13:48:06 |
 Jonas Chevalier | In reply to @pwychowaniec:matrix.org
hi, do we have any procedure for deprecating nix-community projects? 👀
(or at least changing status to looking for maintainer) which project are you thinking of? we don't have an official procedure, but posting it to this channel is a good start | 15:42:52 |
| pwychowaniec | https://github.com/nix-community/naersk
I've been maintaining it for a while now, but I've currently run out of time, so it would be nice to find someone to take over 🙂 (or deprecate in favor of https://github.com/ipetkov/crane) | 15:44:40 |
| Jonas Chevalier | do you have anybody in mind that contributed recently? | 15:46:04 |
| Jonas Chevalier | but yeah, maybe crane is the next best thing | 15:46:27 |
| Jonas Chevalier | probably the best thing is to create an issue "looking for a maintainer" in the repo, and then tag people that you think might be interested | 15:47:20 |
| pwychowaniec | I don't have anybody at mind - but creating a dedicated issue sounds like the way to go :-) | 16:04:23 |
| 17 Oct 2023 |
|  Marillindië joined the room. | 07:47:40 |
|  camocatx joined the room. | 22:15:00 |
| 18 Oct 2023 |
|  ghishadow changed their profile picture. | 12:52:00 |
| 21 Oct 2023 |
|  Phobos changed their display name from Faust to Phobos. | 08:00:10 |
| Phobos changed their profile picture. | 08:00:21 |
| 22 Oct 2023 |
|  stroove joined the room. | 23:39:00 |
| 23 Oct 2023 |
|  globin joined the room. | 09:03:42 |
| globin set a profile picture. | 14:27:46 |
| 24 Oct 2023 |
| pwychowaniec changed their profile picture. | 05:25:44 |
 Mic92 | adisbladis: if you had to implement incremental go builds with nix (or just having the dependencies pre-compiled), how would approach the problem? | 17:15:23 |
| 25 Oct 2023 |
|  @federicodschonborn:matrix.org changed their profile picture. | 00:12:41 |
| 26 Oct 2023 |
|  axel 🦀 joined the room. | 03:03:41 |
| axel 🦀 | Hey @pwychowaniec, would it be alright if I dmed you? | 03:16:37 |
| pwychowaniec | sure, sure! | 05:02:12 |
 adisbladis | In reply to @joerg:thalheim.io
adisbladis: if you had to implement incremental go builds with nix (or just having the dependencies pre-compiled), how would approach the problem? I looked into that a while back and my conclusion is that it's not really feasible. But I hope I'm wrong. | 06:38:11 |
|  @lotte:chir.rs changed their profile picture. | 06:46:50 |
| Mic92 | In reply to @adis:blad.is
I looked into that a while back and my conclusion is that it's not really feasible. But I hope I'm wrong. Shouldn't building a cache like this work?
$ export GOCACHE=$out
$ xargs < packages-to-build go install | 06:56:33 |
| Mic92 | and than feed this GOCACHE into the final build again. | 06:57:00 |
| 27 Oct 2023 |
| adisbladis | Mic92: I experimented with doing that in various configurations but it didn't actually end up faster. I can't remember what the issue(s) were. | 00:49:50 |
| @federicodschonborn:matrix.org changed their profile picture. | 01:24:19 |
| pwychowaniec | Jonas Chevalier: axel 🦀 has volunteered for maintaining Naersk - do you know what are the next steps here to implement this? 😄 | 05:41:15 |
| Mic92 | adisbladis: https://github.com/numtide/build-go-cache | 06:34:56 |
| adisbladis | In reply to @joerg:thalheim.io
adisbladis: https://github.com/numtide/build-go-cache Right, so you get one massive cache for the whole project, not any incrementality? | 06:36:06 |
