| 1 Jul 2025 |
 emily | and we'll also need to do a merge into staging-next and staging when we land | 17:33:31 |
| emily | as in, make it a nop in staging | 17:33:51 |
| emily | sorry for not catching that originally | 17:34:00 |
| emily | btw, you may want to collapse newlines for the
cargoHash = "foo";
useFetchCargoVendor = true;
otherThing = 123;
case
| 17:34:37 |
| emily | (not sure if we have any in tree or not though) | 17:34:40 |
| emily | (and actually I guess nixfmt might collapse those already) | 17:34:47 |
 Toma | yes | 17:34:52 |
| Toma | * yes it does | 17:35:06 |
| Toma | Okay, I'll work on the make-NOOP PR then | 17:35:53 |
| Toma | https://github.com/NixOS/nixpkgs/pull/421563 | 17:41:39 |
| Toma | this minimal change should be fine I think | 17:42:13 |
| Toma | Oh it has an eval error, will fix it in a minute | 17:45:43 |
| Toma | * Oh it has an eval error, will fix it in a minute
Edit: Done! | 17:47:57 |
|  DynamicGoose joined the room. | 20:31:06 |
| DynamicGoose set a profile picture. | 20:35:21 |
| 2 Jul 2025 |
|  @michael.zeagler:matrix.org left the room. | 02:12:23 |
|  Markus Theil joined the room. | 13:30:16 |
| 3 Jul 2025 |
|  Robert Rose - 🌴 04.07 changed their display name from Robert Rose to Robert Rose - 🌴 04.07. | 20:37:07 |
| Toma | I would like to revive some conversation around https://github.com/NixOS/nixpkgs/pull/387337
Currently the implementation creates a new subdirectory for each unique source that can be found in the lockfile
Here's an example of how the final directory layout might look like:
$ ls -A result/
.cargo source-git-0 source-git-1 source-git-2 source-registry-0 Cargo.lock
$ cat result/.cargo/config.toml
[source._vendored-source-registry-0]
directory = "@vendor@/source-registry-0"
[source.crates-io]
replace-with = "_vendored-source-registry-0"
[source._vendored-source-git-0]
directory = "@vendor@/source-git-0"
[source._original-source-git-0]
git = "https://github.com/biomejs/biome"
rev = "2648fa4201be4afd26f44eca1a4e77aac0a67272"
replace-with = "_vendored-source-git-0"
[source._vendored-source-git-1]
directory = "@vendor@/source-git-1"
[source._original-source-git-1]
git = "https://github.com/lionel-/tower-lsp"
branch = "bugfix/patches"
replace-with = "_vendored-source-git-1"
[source._vendored-source-git-2]
directory = "@vendor@/source-git-2"
[source._original-source-git-2]
git = "https://github.com/r-lib/tree-sitter-r"
rev = "a0d3e3307489c3ca54da8c7b5b4e0c5f5fd6953a"
replace-with = "_vendored-source-git-2"
| 22:41:21 |
| Toma | I'm also wondering whether we want to support fetching from other registries in the future.
This would require some ret-con on the layout of the FOD itself, but it shouldn't be too bad. | 22:42:38 |
| Toma | * I would like to revive some conversation around https://github.com/NixOS/nixpkgs/pull/387337
Currently PR's implementation creates a new subdirectory for each unique source that can be found in the lockfile
Here's an example of how the final directory layout might look like:
$ ls -A result/
.cargo source-git-0 source-git-1 source-git-2 source-registry-0 Cargo.lock
$ cat result/.cargo/config.toml
[source._vendored-source-registry-0]
directory = "@vendor@/source-registry-0"
[source.crates-io]
replace-with = "_vendored-source-registry-0"
[source._vendored-source-git-0]
directory = "@vendor@/source-git-0"
[source._original-source-git-0]
git = "https://github.com/biomejs/biome"
rev = "2648fa4201be4afd26f44eca1a4e77aac0a67272"
replace-with = "_vendored-source-git-0"
[source._vendored-source-git-1]
directory = "@vendor@/source-git-1"
[source._original-source-git-1]
git = "https://github.com/lionel-/tower-lsp"
branch = "bugfix/patches"
replace-with = "_vendored-source-git-1"
[source._vendored-source-git-2]
directory = "@vendor@/source-git-2"
[source._original-source-git-2]
git = "https://github.com/r-lib/tree-sitter-r"
rev = "a0d3e3307489c3ca54da8c7b5b4e0c5f5fd6953a"
replace-with = "_vendored-source-git-2"
| 22:43:03 |
| Toma | * I would like to revive some conversation around https://github.com/NixOS/nixpkgs/pull/387337
Currently the PR's implementation creates a new subdirectory for each unique source that can be found in the lockfile
Here's an example of how the final directory layout might look like:
$ ls -A result/
.cargo source-git-0 source-git-1 source-git-2 source-registry-0 Cargo.lock
$ cat result/.cargo/config.toml
[source._vendored-source-registry-0]
directory = "@vendor@/source-registry-0"
[source.crates-io]
replace-with = "_vendored-source-registry-0"
[source._vendored-source-git-0]
directory = "@vendor@/source-git-0"
[source._original-source-git-0]
git = "https://github.com/biomejs/biome"
rev = "2648fa4201be4afd26f44eca1a4e77aac0a67272"
replace-with = "_vendored-source-git-0"
[source._vendored-source-git-1]
directory = "@vendor@/source-git-1"
[source._original-source-git-1]
git = "https://github.com/lionel-/tower-lsp"
branch = "bugfix/patches"
replace-with = "_vendored-source-git-1"
[source._vendored-source-git-2]
directory = "@vendor@/source-git-2"
[source._original-source-git-2]
git = "https://github.com/r-lib/tree-sitter-r"
rev = "a0d3e3307489c3ca54da8c7b5b4e0c5f5fd6953a"
replace-with = "_vendored-source-git-2"
| 22:43:12 |
| emily | does anything in practice use multiple registries? | 22:45:47 |
| Toma | Probably people using some internal packages, idk | 22:46:35 |
| Toma | Also even if they were to use multiple registries, in most cases there wouldn't be any clash, so we could just put everything into the tarballs/ directory of the FOD. | 22:48:37 |
| Toma | Btw I have https://github.com/NixOS/nixpkgs/pull/399775 which already has a POC implementation for using multiple registries (though it doesn't put everything into tarballs/) | 22:50:23 |
| 4 Jul 2025 |
|  JacoMalan1 joined the room. | 13:48:28 |
| 5 Jul 2025 |
|  PBlue3 joined the room. | 18:02:54 |
|  kwiuu joined the room. | 20:42:27 |
| 6 Jul 2025 |
| JacoMalan1 changed their display name from jacom to JacoMalan1. | 12:16:13 |
