2019-06-04 17:45:16 +00:00
|
|
|
#pragma once
|
|
|
|
|
2019-02-12 17:23:11 +00:00
|
|
|
#include "types.hh"
|
|
|
|
#include "flakeref.hh"
|
2019-06-04 18:01:21 +00:00
|
|
|
#include "lockfile.hh"
|
2020-04-16 14:54:34 +00:00
|
|
|
#include "value.hh"
|
2019-02-12 17:23:11 +00:00
|
|
|
|
|
|
|
namespace nix {
|
|
|
|
|
2019-05-29 13:31:07 +00:00
|
|
|
class EvalState;
|
|
|
|
|
2020-01-21 15:27:53 +00:00
|
|
|
namespace fetchers { struct Tree; }
|
2019-05-21 12:55:43 +00:00
|
|
|
|
2020-01-21 15:27:53 +00:00
|
|
|
namespace flake {
|
2019-03-10 06:05:05 +00:00
|
|
|
|
Respect lock files of inputs + fine-grained lock file control
When computing a lock file, we now respect the lock files of flake
inputs. This is important for usability / reproducibility. For
example, the 'nixops' flake depends on the 'nixops-aws' and
'nixops-hetzner' repositories. So when the 'nixops' flake is used in
another flake, we want the versions of 'nixops-aws' and
'nixops-hetzner' locked by the the 'nixops' flake because those
presumably have been tested.
This can lead to a proliferation of versions of flakes like 'nixpkgs'
(since every flake's lock file could depend on a different version of
'nixpkgs'). This is not a major issue when using Nixpkgs overlays or
NixOS modules, since then the top-level flake composes those
overlays/modules into *its* version of Nixpkgs and all other versions
are ignored. Lock file computation has been made a bit more lazy so it
won't try to fetch all those versions of 'nixpkgs'.
However, in case it's necessary to minimize flake versions, there now
are two input attributes that allow this. First, you can copy an input
from another flake, as follows:
inputs.nixpkgs.follows = "dwarffs/nixpkgs";
This states that the calling flake's 'nixpkgs' input shall be the same
as the 'nixpkgs' input of the 'dwarffs' input.
Second, you can override inputs of inputs:
inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
inputs.nixops.inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
or equivalently, using 'follows':
inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
inputs.nixops.inputs.nixpkgs.follows = "nixpkgs";
This states that the 'nixpkgs' input of the 'nixops' input shall be
the same as the calling flake's 'nixpkgs' input.
Finally, at '-v' Nix now prints the changes to the lock file, e.g.
$ nix flake update ~/Misc/eelco-configurations/hagbard
inputs of flake 'git+file:///home/eelco/Misc/eelco-configurations?subdir=hagbard' changed:
updated 'nixpkgs': 'github:edolstra/nixpkgs/7845bf5f4b3013df1cf036e9c9c3a55a30331db9' -> 'github:edolstra/nixpkgs/03f3def66a104a221aac8b751eeb7075374848fd'
removed 'nixops'
removed 'nixops/nixops-aws'
removed 'nixops/nixops-hetzner'
removed 'nixops/nixpkgs'
2020-01-24 21:05:11 +00:00
|
|
|
struct FlakeInput;
|
|
|
|
|
|
|
|
typedef std::map<FlakeId, FlakeInput> FlakeInputs;
|
|
|
|
|
2020-09-28 16:37:26 +00:00
|
|
|
/* FlakeInput is the 'Flake'-level parsed form of the "input" entries
|
|
|
|
* in the flake file.
|
|
|
|
*
|
|
|
|
* A FlakeInput is normally constructed by the 'parseFlakeInput'
|
|
|
|
* function which parses the input specification in the '.flake' file
|
|
|
|
* to create a 'FlakeRef' (a fetcher, the fetcher-specific
|
|
|
|
* representation of the input specification, and possibly the fetched
|
|
|
|
* local store path result) and then creating this FlakeInput to hold
|
|
|
|
* that FlakeRef, along with anything that might override that
|
|
|
|
* FlakeRef (like command-line overrides or "follows" specifications).
|
|
|
|
*
|
|
|
|
* A FlakeInput is also sometimes constructed directly from a FlakeRef
|
|
|
|
* instead of starting at the flake-file input specification
|
|
|
|
* (e.g. overrides, follows, and implicit inputs).
|
|
|
|
*
|
|
|
|
* A FlakeInput will usually have one of either "ref" or "follows"
|
|
|
|
* set. If not otherwise specified, a "ref" will be generated to a
|
|
|
|
* 'type="indirect"' flake, which is treated as simply the name of a
|
|
|
|
* flake to be resolved in the registry.
|
|
|
|
*/
|
2020-09-26 21:32:58 +00:00
|
|
|
|
2019-08-30 14:27:51 +00:00
|
|
|
struct FlakeInput
|
|
|
|
{
|
2020-06-11 12:40:21 +00:00
|
|
|
std::optional<FlakeRef> ref;
|
2020-09-26 21:32:58 +00:00
|
|
|
bool isFlake = true; // true = process flake to get outputs, false = (fetched) static source path
|
Respect lock files of inputs + fine-grained lock file control
When computing a lock file, we now respect the lock files of flake
inputs. This is important for usability / reproducibility. For
example, the 'nixops' flake depends on the 'nixops-aws' and
'nixops-hetzner' repositories. So when the 'nixops' flake is used in
another flake, we want the versions of 'nixops-aws' and
'nixops-hetzner' locked by the the 'nixops' flake because those
presumably have been tested.
This can lead to a proliferation of versions of flakes like 'nixpkgs'
(since every flake's lock file could depend on a different version of
'nixpkgs'). This is not a major issue when using Nixpkgs overlays or
NixOS modules, since then the top-level flake composes those
overlays/modules into *its* version of Nixpkgs and all other versions
are ignored. Lock file computation has been made a bit more lazy so it
won't try to fetch all those versions of 'nixpkgs'.
However, in case it's necessary to minimize flake versions, there now
are two input attributes that allow this. First, you can copy an input
from another flake, as follows:
inputs.nixpkgs.follows = "dwarffs/nixpkgs";
This states that the calling flake's 'nixpkgs' input shall be the same
as the 'nixpkgs' input of the 'dwarffs' input.
Second, you can override inputs of inputs:
inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
inputs.nixops.inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
or equivalently, using 'follows':
inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
inputs.nixops.inputs.nixpkgs.follows = "nixpkgs";
This states that the 'nixpkgs' input of the 'nixops' input shall be
the same as the calling flake's 'nixpkgs' input.
Finally, at '-v' Nix now prints the changes to the lock file, e.g.
$ nix flake update ~/Misc/eelco-configurations/hagbard
inputs of flake 'git+file:///home/eelco/Misc/eelco-configurations?subdir=hagbard' changed:
updated 'nixpkgs': 'github:edolstra/nixpkgs/7845bf5f4b3013df1cf036e9c9c3a55a30331db9' -> 'github:edolstra/nixpkgs/03f3def66a104a221aac8b751eeb7075374848fd'
removed 'nixops'
removed 'nixops/nixops-aws'
removed 'nixops/nixops-hetzner'
removed 'nixops/nixpkgs'
2020-01-24 21:05:11 +00:00
|
|
|
std::optional<InputPath> follows;
|
2020-06-11 12:40:21 +00:00
|
|
|
bool absolute = false; // whether 'follows' is relative to the flake root
|
Respect lock files of inputs + fine-grained lock file control
When computing a lock file, we now respect the lock files of flake
inputs. This is important for usability / reproducibility. For
example, the 'nixops' flake depends on the 'nixops-aws' and
'nixops-hetzner' repositories. So when the 'nixops' flake is used in
another flake, we want the versions of 'nixops-aws' and
'nixops-hetzner' locked by the the 'nixops' flake because those
presumably have been tested.
This can lead to a proliferation of versions of flakes like 'nixpkgs'
(since every flake's lock file could depend on a different version of
'nixpkgs'). This is not a major issue when using Nixpkgs overlays or
NixOS modules, since then the top-level flake composes those
overlays/modules into *its* version of Nixpkgs and all other versions
are ignored. Lock file computation has been made a bit more lazy so it
won't try to fetch all those versions of 'nixpkgs'.
However, in case it's necessary to minimize flake versions, there now
are two input attributes that allow this. First, you can copy an input
from another flake, as follows:
inputs.nixpkgs.follows = "dwarffs/nixpkgs";
This states that the calling flake's 'nixpkgs' input shall be the same
as the 'nixpkgs' input of the 'dwarffs' input.
Second, you can override inputs of inputs:
inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
inputs.nixops.inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
or equivalently, using 'follows':
inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
inputs.nixops.inputs.nixpkgs.follows = "nixpkgs";
This states that the 'nixpkgs' input of the 'nixops' input shall be
the same as the calling flake's 'nixpkgs' input.
Finally, at '-v' Nix now prints the changes to the lock file, e.g.
$ nix flake update ~/Misc/eelco-configurations/hagbard
inputs of flake 'git+file:///home/eelco/Misc/eelco-configurations?subdir=hagbard' changed:
updated 'nixpkgs': 'github:edolstra/nixpkgs/7845bf5f4b3013df1cf036e9c9c3a55a30331db9' -> 'github:edolstra/nixpkgs/03f3def66a104a221aac8b751eeb7075374848fd'
removed 'nixops'
removed 'nixops/nixops-aws'
removed 'nixops/nixops-hetzner'
removed 'nixops/nixpkgs'
2020-01-24 21:05:11 +00:00
|
|
|
FlakeInputs overrides;
|
2019-08-30 14:27:51 +00:00
|
|
|
};
|
|
|
|
|
2020-10-26 19:45:39 +00:00
|
|
|
struct ConfigFile
|
|
|
|
{
|
|
|
|
using ConfigValue = std::variant<std::string, int64_t, Explicit<bool>, std::vector<std::string>>;
|
|
|
|
|
2020-11-26 11:34:43 +00:00
|
|
|
std::map<std::string, ConfigValue> settings;
|
2020-10-26 19:45:39 +00:00
|
|
|
|
|
|
|
void apply();
|
|
|
|
};
|
2020-09-26 21:32:58 +00:00
|
|
|
|
2020-10-26 19:45:39 +00:00
|
|
|
/* The contents of a flake.nix file. */
|
2019-02-21 05:53:01 +00:00
|
|
|
struct Flake
|
|
|
|
{
|
2020-09-26 21:32:58 +00:00
|
|
|
FlakeRef originalRef; // the original flake specification (by the user)
|
|
|
|
FlakeRef resolvedRef; // registry references and caching resolved to the specific underlying flake
|
|
|
|
FlakeRef lockedRef; // the specific local store result of invoking the fetcher
|
2020-01-22 16:20:21 +00:00
|
|
|
std::optional<std::string> description;
|
2020-01-21 15:27:53 +00:00
|
|
|
std::shared_ptr<const fetchers::Tree> sourceInfo;
|
Respect lock files of inputs + fine-grained lock file control
When computing a lock file, we now respect the lock files of flake
inputs. This is important for usability / reproducibility. For
example, the 'nixops' flake depends on the 'nixops-aws' and
'nixops-hetzner' repositories. So when the 'nixops' flake is used in
another flake, we want the versions of 'nixops-aws' and
'nixops-hetzner' locked by the the 'nixops' flake because those
presumably have been tested.
This can lead to a proliferation of versions of flakes like 'nixpkgs'
(since every flake's lock file could depend on a different version of
'nixpkgs'). This is not a major issue when using Nixpkgs overlays or
NixOS modules, since then the top-level flake composes those
overlays/modules into *its* version of Nixpkgs and all other versions
are ignored. Lock file computation has been made a bit more lazy so it
won't try to fetch all those versions of 'nixpkgs'.
However, in case it's necessary to minimize flake versions, there now
are two input attributes that allow this. First, you can copy an input
from another flake, as follows:
inputs.nixpkgs.follows = "dwarffs/nixpkgs";
This states that the calling flake's 'nixpkgs' input shall be the same
as the 'nixpkgs' input of the 'dwarffs' input.
Second, you can override inputs of inputs:
inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
inputs.nixops.inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
or equivalently, using 'follows':
inputs.nixpkgs.url = github:edolstra/nixpkgs/<hash>;
inputs.nixops.inputs.nixpkgs.follows = "nixpkgs";
This states that the 'nixpkgs' input of the 'nixops' input shall be
the same as the calling flake's 'nixpkgs' input.
Finally, at '-v' Nix now prints the changes to the lock file, e.g.
$ nix flake update ~/Misc/eelco-configurations/hagbard
inputs of flake 'git+file:///home/eelco/Misc/eelco-configurations?subdir=hagbard' changed:
updated 'nixpkgs': 'github:edolstra/nixpkgs/7845bf5f4b3013df1cf036e9c9c3a55a30331db9' -> 'github:edolstra/nixpkgs/03f3def66a104a221aac8b751eeb7075374848fd'
removed 'nixops'
removed 'nixops/nixops-aws'
removed 'nixops/nixops-hetzner'
removed 'nixops/nixpkgs'
2020-01-24 21:05:11 +00:00
|
|
|
FlakeInputs inputs;
|
2020-10-26 19:45:39 +00:00
|
|
|
ConfigFile config; // 'nixConfig' attribute
|
2020-01-21 15:27:53 +00:00
|
|
|
~Flake();
|
2019-03-21 08:30:16 +00:00
|
|
|
};
|
|
|
|
|
2019-09-18 19:17:27 +00:00
|
|
|
Flake getFlake(EvalState & state, const FlakeRef & flakeRef, bool allowLookup);
|
2019-06-21 17:04:58 +00:00
|
|
|
|
2019-06-07 20:25:48 +00:00
|
|
|
/* Fingerprint of a locked flake; used as a cache key. */
|
|
|
|
typedef Hash Fingerprint;
|
|
|
|
|
2020-01-22 19:59:59 +00:00
|
|
|
struct LockedFlake
|
2019-03-21 08:30:16 +00:00
|
|
|
{
|
2019-03-29 15:18:25 +00:00
|
|
|
Flake flake;
|
2019-06-04 17:10:35 +00:00
|
|
|
LockFile lockFile;
|
2019-06-07 20:25:48 +00:00
|
|
|
|
|
|
|
Fingerprint getFingerprint() const;
|
2019-03-21 08:30:16 +00:00
|
|
|
};
|
|
|
|
|
2020-01-29 13:57:57 +00:00
|
|
|
struct LockFlags
|
|
|
|
{
|
2020-01-29 20:01:34 +00:00
|
|
|
/* Whether to ignore the existing lock file, creating a new one
|
|
|
|
from scratch. */
|
|
|
|
bool recreateLockFile = false;
|
|
|
|
|
|
|
|
/* Whether to update the lock file at all. If set to false, if any
|
|
|
|
change to the lock file is needed (e.g. when an input has been
|
|
|
|
added to flake.nix), you get a fatal error. */
|
|
|
|
bool updateLockFile = true;
|
|
|
|
|
|
|
|
/* Whether to write the lock file to disk. If set to true, if the
|
|
|
|
any changes to the lock file are needed and the flake is not
|
|
|
|
writable (i.e. is not a local Git working tree or similar), you
|
|
|
|
get a fatal error. If set to false, Nix will use the modified
|
|
|
|
lock file in memory only, without writing it to disk. */
|
|
|
|
bool writeLockFile = true;
|
|
|
|
|
|
|
|
/* Whether to use the registries to lookup indirect flake
|
|
|
|
references like 'nixpkgs'. */
|
|
|
|
bool useRegistries = true;
|
|
|
|
|
|
|
|
/* Whether mutable flake references (i.e. those without a Git
|
|
|
|
revision or similar) without a corresponding lock are
|
|
|
|
allowed. Mutable flake references with a lock are always
|
|
|
|
allowed. */
|
|
|
|
bool allowMutable = true;
|
|
|
|
|
2020-02-05 13:48:49 +00:00
|
|
|
/* Whether to commit changes to flake.lock. */
|
|
|
|
bool commitLockFile = false;
|
|
|
|
|
2021-03-26 15:14:38 +00:00
|
|
|
/* Flake inputs to be overridden. */
|
2020-01-29 13:57:57 +00:00
|
|
|
std::map<InputPath, FlakeRef> inputOverrides;
|
2020-01-29 22:12:58 +00:00
|
|
|
|
|
|
|
/* Flake inputs to be updated. This means that any existing lock
|
|
|
|
for those inputs will be ignored. */
|
|
|
|
std::set<InputPath> inputUpdates;
|
2020-01-29 13:57:57 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
LockedFlake lockFlake(
|
2020-01-29 20:01:34 +00:00
|
|
|
EvalState & state,
|
|
|
|
const FlakeRef & flakeRef,
|
|
|
|
const LockFlags & lockFlags);
|
2019-04-16 12:27:54 +00:00
|
|
|
|
2020-01-29 20:01:34 +00:00
|
|
|
void callFlake(
|
|
|
|
EvalState & state,
|
2020-03-12 21:06:57 +00:00
|
|
|
const LockedFlake & lockedFlake,
|
2019-06-04 17:10:35 +00:00
|
|
|
Value & v);
|
2019-05-23 21:42:13 +00:00
|
|
|
|
2019-02-12 17:23:11 +00:00
|
|
|
}
|
2019-05-29 13:31:07 +00:00
|
|
|
|
2020-03-09 14:28:41 +00:00
|
|
|
void emitTreeAttrs(
|
|
|
|
EvalState & state,
|
|
|
|
const fetchers::Tree & tree,
|
Remove TreeInfo
The attributes previously stored in TreeInfo (narHash, revCount,
lastModified) are now stored in Input. This makes it less arbitrary
what attributes are stored where.
As a result, the lock file format has changed. An entry like
"info": {
"lastModified": 1585405475,
"narHash": "sha256-bESW0n4KgPmZ0luxvwJ+UyATrC6iIltVCsGdLiphVeE="
},
"locked": {
"owner": "NixOS",
"repo": "nixpkgs",
"rev": "b88ff468e9850410070d4e0ccd68c7011f15b2be",
"type": "github"
},
is now stored as
"locked": {
"owner": "NixOS",
"repo": "nixpkgs",
"rev": "b88ff468e9850410070d4e0ccd68c7011f15b2be",
"type": "github",
"lastModified": 1585405475,
"narHash": "sha256-bESW0n4KgPmZ0luxvwJ+UyATrC6iIltVCsGdLiphVeE="
},
The 'Input' class is now a dumb set of attributes. All the fetcher
implementations subclass InputScheme, not Input. This simplifies the
API.
Also, fix substitution of flake inputs. This was broken since lazy
flake fetching started using fetchTree internally.
2020-05-29 22:44:11 +00:00
|
|
|
const fetchers::Input & input,
|
2020-07-28 20:46:39 +00:00
|
|
|
Value & v, bool emptyRevFallback = false);
|
2020-03-09 14:28:41 +00:00
|
|
|
|
2019-05-29 13:31:07 +00:00
|
|
|
}
|