Hi All. Not sure if this is a good place to ask but I would imagine this group has spent a bit more time groking the details of the host -> target dependency theory from the nixpkgs manual. Is this correct?

let mapOffset(h, t, i) = i + (if i <= 0 then h else t - 1)

dep(h0, t0, A, B)
propagated-dep(h1, t1, B, C)
h0 + h1 in {-1, 0, 1}
h0 + t1 in {-1, 0, -1}
----------------------------- Take immediate dependencies' propagated dependencies
propagated-dep(mapOffset(h0, t0, h1),
               mapOffset(h0, t0, t1),
               A, C)

shouldn't the final line be just dep instead of propagated-dep ?
because otherwise I think a propagatedBuildInputs would be propagated across a whole buildInputs chain.
eg if propagated-dep(0, 1, C, D), dep(0, 1, B, C), dep(0, 1, A, B) then this results in propagated-dep(0, 1, B, D), propagated-dep(0, 1, A, D)

In reply to @rosscomputerguy:matrix.org
Fun...

In reply to @rosscomputerguy:matrix.org
Fun...

Anyone else wondering what I'm talking about it's these two derivations: (nixpkgs @ 087408a407440892c1b00d80360fd64639b8091d)

nix-store --query -R $(nix-instantiate --system aarch64-darwin -A llvmPackages) | grep llvm-src-16
/nix/store/g0w6vxlsapnd0asv939aj8pdwjbqj2mm-llvm-src-16.0.6.drv
/nix/store/yhzv33cm9bx6sb5i0pvz4s9ikll4sgaj-llvm-src-16.0.6.drv

Randy Eckenrode

In reply to @reckenrode:matrix.org
I would be surprised if that’s what is happening with lldbPlugins unless it’s somehow accidentally capturing a package from the bootstrap that isn’t build otherwise.