We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resolveFlake must be able to handle 6 use cases for what to do with the lockfile:
resolveFlake
prim_getFlake
LockFile
nix build dwarffs
nix build ~/nix/dwarffs
FlakeRef
IsPath
nix build ~/nix/dwarffs --no-save-lock-file
nix build X --recreate-lock-file
nix flake update
In order to implement this, I will create an enum
enum HandleLockFile { AllPure, UpdateLockFile, UseUpdatedLockFile, RecreateLockFile, UseNewLockFile};
with two helper functions
bool allowedToWrite (HandleLockFile handle); bool recreateLockFile (HandleLockFile handle);
resolveFlake now gets an argument HandleLockFile.
HandleLockFile
The text was updated successfully, but these errors were encountered:
CSVdB
No branches or pull requests
resolveFlake
must be able to handle 6 use cases for what to do with the lockfile:prim_getFlake
while pure: In this case, everything is handled purely, so no registries, no updatingLockFile
, no writingLockFile
to file.nix build dwarffs
: UpdateLockFile
before usagenix build ~/nix/dwarffs
: UpdateLockFile
before usage, and save it to file. This is only if the installable is aFlakeRef
withIsPath
.nix build ~/nix/dwarffs --no-save-lock-file
: UpdateLockFile
before usage, and don't save it to filenix build X --recreate-lock-file
: Same as above (depending on what X is), but recreate theLockFile
from scratchnix flake update
: Same as case 5In order to implement this, I will create an enum
with two helper functions
resolveFlake
now gets an argumentHandleLockFile
.The text was updated successfully, but these errors were encountered: