2021-03-02 02:47:00 +02:00
|
|
|
#pragma once
|
2023-04-01 06:18:41 +03:00
|
|
|
///@file
|
2021-03-02 02:47:00 +02:00
|
|
|
|
|
|
|
#include "path.hh"
|
2021-04-05 17:33:28 +03:00
|
|
|
#include "derived-path.hh"
|
2021-03-02 02:47:00 +02:00
|
|
|
|
|
|
|
namespace nix {
|
|
|
|
|
2023-04-07 16:55:28 +03:00
|
|
|
/**
|
|
|
|
* This is a deprecated old type just for use by the old CLI, and older
|
|
|
|
* versions of the RPC protocols. In new code don't use it; you want
|
|
|
|
* `DerivedPath` instead.
|
|
|
|
*
|
|
|
|
* `DerivedPath` is better because it handles more cases, and does so more
|
|
|
|
* explicitly without devious punning tricks.
|
|
|
|
*/
|
2021-03-02 02:47:00 +02:00
|
|
|
struct StorePathWithOutputs
|
|
|
|
{
|
|
|
|
StorePath path;
|
|
|
|
std::set<std::string> outputs;
|
|
|
|
|
|
|
|
std::string to_string(const Store & store) const;
|
2021-03-02 05:50:41 +02:00
|
|
|
|
2021-04-05 16:48:18 +03:00
|
|
|
DerivedPath toDerivedPath() const;
|
2021-03-02 05:50:41 +02:00
|
|
|
|
Make the Derived Path family of types inductive for dynamic derivations
We want to be able to write down `foo.drv^bar.drv^baz`:
`foo.drv^bar.drv` is the dynamic derivation (since it is itself a
derivation output, `bar.drv` from `foo.drv`).
To that end, we create `Single{Derivation,BuiltPath}` types, that are
very similar except instead of having multiple outputs (in a set or
map), they have a single one. This is for everything to the left of the
rightmost `^`.
`NixStringContextElem` has an analogous change, and now can reuse
`SingleDerivedPath` at the top level. In fact, if we ever get rid of
`DrvDeep`, `NixStringContextElem` could be replaced with
`SingleDerivedPath` entirely!
Important note: some JSON formats have changed.
We already can *produce* dynamic derivations, but we can't refer to them
directly. Today, we can merely express building or example at the top
imperatively over time by building `foo.drv^bar.drv`, and then with a
second nix invocation doing `<result-from-first>^baz`, but this is not
declarative. The ethos of Nix of being able to write down the full plan
everything you want to do, and then execute than plan with a single
command, and for that we need the new inductive form of these types.
Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2023-01-16 00:39:04 +02:00
|
|
|
typedef std::variant<StorePathWithOutputs, StorePath, std::monostate> ParseResult;
|
|
|
|
|
|
|
|
static StorePathWithOutputs::ParseResult tryFromDerivedPath(const DerivedPath &);
|
2021-03-02 02:47:00 +02:00
|
|
|
};
|
|
|
|
|
2021-04-05 16:48:18 +03:00
|
|
|
std::vector<DerivedPath> toDerivedPaths(const std::vector<StorePathWithOutputs>);
|
2021-03-02 05:50:41 +02:00
|
|
|
|
2021-03-02 02:47:00 +02:00
|
|
|
std::pair<std::string_view, StringSet> parsePathWithOutputs(std::string_view s);
|
|
|
|
|
2021-03-02 03:06:08 +02:00
|
|
|
class Store;
|
|
|
|
|
2023-04-07 16:55:28 +03:00
|
|
|
/**
|
|
|
|
* Split a string specifying a derivation and a set of outputs
|
|
|
|
* (/nix/store/hash-foo!out1,out2,...) into the derivation path
|
|
|
|
* and the outputs.
|
|
|
|
*/
|
2021-03-02 03:06:08 +02:00
|
|
|
StorePathWithOutputs parsePathWithOutputs(const Store & store, std::string_view pathWithOutputs);
|
|
|
|
|
|
|
|
StorePathWithOutputs followLinksToStorePathWithOutputs(const Store & store, std::string_view pathWithOutputs);
|
|
|
|
|
2021-03-02 02:47:00 +02:00
|
|
|
}
|