diff options
Diffstat (limited to 'doc/future-designs')
| -rw-r--r-- | doc/future-designs/computed-roots.org | 6 | ||||
| -rw-r--r-- | doc/future-designs/service-target-cache.org | 4 |
2 files changed, 5 insertions, 5 deletions
diff --git a/doc/future-designs/computed-roots.org b/doc/future-designs/computed-roots.org index d3c355ce..a83eee67 100644 --- a/doc/future-designs/computed-roots.org +++ b/doc/future-designs/computed-roots.org @@ -60,7 +60,7 @@ file, so that it can be used during analysis. Still, the information is already present in the prebuilt binary, causing unnecessary maintenance overhead; instead, the target file could be a function of that library which can form its own content-fixed root (e.g., a -~git tree~ root), so that the computed value is easily cachable. +~git tree~ root), so that the computed value is easily cacheable. *** Simplified rule definition and alternative syntax @@ -78,14 +78,14 @@ but people argue that it is hard to write by hand. However, it is unlikely to get agreement on which syntax is best to use. Now, if rule and expression files could be generated, this argument would not be necessary. Moreover, rules are typically versioned and -unfrequently changed, so the step of generating the official syntax +infrequently changed, so the step of generating the official syntax from the convenient one would typically be in cache. ** Proposal: Support computed roots We propose computed roots as a clean principle to add the needed (and a lot more) flexibility for the described use cases, while ensuring -that all computations of roots are properly cachable at high level. +that all computations of roots are properly cacheable at high level. In this way, we do not compromise efficient builds, as the price of the additional flexibility, in the typical case, is just a single cache lookup. Of course, it is up to the user to ensure that this diff --git a/doc/future-designs/service-target-cache.org b/doc/future-designs/service-target-cache.org index 9f07351d..10138db5 100644 --- a/doc/future-designs/service-target-cache.org +++ b/doc/future-designs/service-target-cache.org @@ -158,7 +158,7 @@ serve~ endpoint has to be specified in the invocation of ~just~. **** ~just-mr~ pragma ~"absent"~ -For ~just-mr~ to know how to contruct the repository description, +For ~just-mr~ to know how to construct the repository description, the description used by ~just-mr~ is extended. More precisely, a new key ~"absent"~ is allowed in the ~"pragma"~ dictionary of a repository description. If the specified value is true, ~just-mr~ @@ -196,7 +196,7 @@ Such a repository is given by - a command that, when executed in an empty directory (anywhere in the file system) will create in that directory a directory structure containing the specified ~git~ tree (either top-level - or in some sudirectory). Moreover, that command does not modify + or in some subdirectory). Moreover, that command does not modify anything outside the directory it is called in; it is an error if the specified tree is not created in this way. In this way, content-fixed repositories can be generated in a |