#include <derived-path.hh>
Public Member Functions | |
const StorePath & | getBaseStorePath () const |
std::string | to_string (const StoreDirConfig &store) const |
std::string | to_string_legacy (const StoreDirConfig &store) const |
nlohmann::json | toJSON (Store &store) const |
bool | operator== (const DerivedPathBuilt &) const noexcept |
bool | operator< (const DerivedPathBuilt &) const noexcept |
Static Public Member Functions | |
static DerivedPathBuilt | parse (const StoreDirConfig &store, ref< SingleDerivedPath >, std::string_view, const ExperimentalFeatureSettings &xpSettings=experimentalFeatureSettings) |
Public Attributes | |
ref< SingleDerivedPath > | drvPath |
OutputsSpec | outputs |
A set of derived paths that are built from a derivation
Built derived paths are pair of a derivation and some output names. They are evaluated by building the derivation, and then replacing the output names with the resulting outputs.
Note that does mean a derived store paths evaluates to multiple opaque paths, which is sort of icky as expressions are supposed to evaluate to single values. Perhaps this should have just a single output name.
const StorePath & nix::DerivedPath::Built::getBaseStorePath | ( | ) | const |
Get the store path this is ultimately derived from (by realising and projecting outputs).
Note that this is not a property of the store object being referred to, but just of this path — how we happened to be referring to that store object. In other words, this means this function breaks "referential transparency". It should therefore be used only with great care.
|
static |
The caller splits on the separator, so it works for both variants.
xpSettings | Stop-gap to avoid globals during unit tests. |
std::string nix::DerivedPath::Built::to_string | ( | const StoreDirConfig & | store | ) | const |
Uses ^
as the separator
std::string nix::DerivedPath::Built::to_string_legacy | ( | const StoreDirConfig & | store | ) | const |
Uses !
as the separator