| 12 May 2026 |
 hexa | yeah, that works | 14:52:10 |
 figsoda | that sounds like the better plan in the long term, but it will still need some bootstrapping (within rust stuff) to work, so you don't have cargo -> fetchCargoVendor -> importCargoLock -> cargo | 14:58:08 |
 Toma | BTW we can also still revive fetchCargoTarball (aka. the internal cargo vendor logic) for internal use only | 20:05:01 |
| 13 May 2026 |
 Pol | I am working onto packaging oxc and the build is very long and it seems that there are a couple of failing tests. Do you have some advice to share to speed up the process ? Currently, I just run nix-build -A oxc then wait 30 minutes, then modify the package.nix file, adding a --skip=... line, then repeat. | 13:15:30 |
| Pol | * I am working onto packaging oxc and the build is very long and it seems that there are a couple of failing tests. Do you have some advice to share to speed up the process ? Currently, I just run nix-build -A oxc then wait 30 minutes, then modify the package.nix file, adding a --skip=... line, then repeat. Is there a trick I could do to restart the build where it was, some kind of "during development mode", just for writing the package.nix file correctly. | 13:41:19 |
| Pol | * I am working onto packaging oxc and the build is very long and it seems that there are a couple of failing tests. Do you have some advice to share to speed up the process ? Currently, I just run nix-build -A oxc then wait 30 minutes, then modify the package.nix file, adding a --skip=... line, then repeat. Is there a trick I could do to restart the build where it was, some kind of "during development mode", just for writing the package.nix file correctly ? | 13:41:27 |
| Pol | * I am working onto packaging oxc (https://github.com/oxc-project/oxc) and the build is very long and it seems that there are a couple of failing tests. Do you have some advice to share to speed up the process ? Currently, I just run nix-build -A oxc then wait 30 minutes, then modify the package.nix file, adding a --skip=... line, then repeat. Is there a trick I could do to restart the build where it was, some kind of "during development mode", just for writing the package.nix file correctly ? | 13:49:40 |
| figsoda | oxc is a monorepo of different tools, we already have oxfmt and oxlint in nixpkgs, what specifically are you looking to package? | 13:57:22 |
| Pol | Oooh it's in there already, shit I must not have seen it | 13:57:48 |
| figsoda | and for development i believe you can nix-shell or nix develop and run the hooks yourself manually | 13:57:57 |
| Pol | #facepalm... | 13:58:04 |
| Pol | Thank you | 13:58:06 |
| 14 May 2026 |
|  @pederbs:pvv.ntnu.no left the room. | 00:23:10 |
