summaryrefslogtreecommitdiff
path: root/doc/concepts/computed-roots.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/concepts/computed-roots.md')
-rw-r--r--doc/concepts/computed-roots.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/concepts/computed-roots.md b/doc/concepts/computed-roots.md
index 171c7648..7007eab4 100644
--- a/doc/concepts/computed-roots.md
+++ b/doc/concepts/computed-roots.md
@@ -136,9 +136,11 @@ of a `"computed"` repository is just forwarded as computed root.
Due to the presence of `just serve`, roots can be absent. This
affects computed roots in two ways,
+
- roots, in particular the target roots, of the repository referred
to can be absent, and
- a computed root can be absent itself.
+
The latter has to be supported, as dependencies that should be
delegated to `just serve` might contain computed roots themselves.
In this case, we consider it acceptable to have one round of talking
@@ -172,12 +174,14 @@ true}]` is the same computed root considered absent.
If a computed root is absent then, in native mode, regardless of whether
the base repository is absent or not,
+
- serve will be asked for the result, and
- from the result the tree identifier of the root will be computed
in memory and the root set to that value, as absent.
If a concrete computed root refers to a base repository with absent
target root,
+
- the client will ask serve about the flexible variables of the
specified target, and
- with this information will compute locally the cache key and