You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But for this repo, that leads to a failing build, because the tensorflow-proto subdir has a relative symlink third_party in it that points to ../third_party - this symlink becomes dangling when only the subdir is copied to the store. (third_party itself happens to have a submodule in it, but that's #44.)
The text was updated successfully, but these errors were encountered:
@isomorpheme Thanks for submitting this, and sorry for taking so long to get to this!
I'm not sure what to do here. This just seems like a tricky corner case. Do you have any suggestions on how to handle this?
It feels like to me that a "nice" solution here probably doesn't exist. The best we could do is add some sort of hook that allows the user to go in and manually fix up the repo definition. But at that point, the user could just add their own overlay on top of the overlay produced by stacklock2nix, so the additional hook seems somewhat pointless.
In
stack.yaml
I have something like:I see that this leads to a different
src
derivation for each subdir here:stacklock2nix/nix/build-support/stacklock2nix/default.nix
Line 390 in 22676df
But for this repo, that leads to a failing build, because the
tensorflow-proto
subdir has a relative symlinkthird_party
in it that points to../third_party
- this symlink becomes dangling when only the subdir is copied to the store. (third_party
itself happens to have a submodule in it, but that's #44.)The text was updated successfully, but these errors were encountered: