Use explicit cross-platform flock rather than impurely referencing it #30
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: tristan/nixinate#30
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "mc/flock-explicit"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This solves #29
Could also use flock from util-linux
@Kranzes Best to avoid locking ourselves into Linux. Right now, technically all of our utilities are not linux specific.
Does nixos-rebuild work on darwin?
@Kranzes No, but I was thinking of having multiple backends, which would solve that problem. So the deployment can be implemented by any backend.
I am having trouble with this change because the locally references nix store path of flock is not available on my target machine, resulting in
But I would not be able to call
nix store --realise /nix/store/wrdk8aqwq7h0lyjglkqgf4x7izd2ymsc-flock-0.2.3/bin/flock
afternix copy
with a file lock usingflock
, some chicken-egg problem here..Should I create a separate issue for it?
@Gerschtli That's interesting, and it should have been caught by my VM Tests, this indicates my VM Tests are not good enough.