| Age | Commit message (Collapse) | Author |
|---|
|
... mentioning that now etc/repos.in.json is used for bootstrapping.
This is relevant for both, determining the precise list of dependencies
needed as well as for patching the repository configuration, e.g.,
in a package build.
|
|
|
|
|
|
|
|
|
|
For a generic rule, it is an error if map union of various
inputs (overlayed in correct order) does not form a proper stage. To
implement this check properly, we first have to construct the map of
all inputs and only then perform the staging check and not do the check
with only the runfiles, as 5e104a526cf76fe75312d2fd288a3c88f506fb0a
accidentally did. Fix this.
|
|
|
|
|
|
Expression language has new built-ins 'zip_with', 'zip_map'.
|
|
... as they will be taken care of only during the build.
|
|
|
|
|
|
|
|
|
|
... documenting fixes since 1.5.0~beta2
|
|
|
|
... documenting the chanages since the first beta release. While there, also
fix the structure of the document and unify use of empty lines.
|
|
To properly use `just serve`, both the client and the serve instance
must talk to the very same execution endpoint. Typically, both the
client and serve can reach out to the execution endpoint via the same
IP address. However, it might be possible that the client and a serve
instance know the same execution endpoint by means of differnet IP
addresses. For example, the client knows the execution endpoint
address through an _external_ IP address, while the serve instance,
deployed within the same network infrastructure, only knows the
_internal_ IP address.
This patch adds the subkey `"client address"` -- of the key
`"execution endpoint"` -- in the serve configuration file, to specify
the alternative pair `address:port` used by the client.
|
|
|
|
Update CHANGELOG accordingly.
|
|
... with entry for new just add-to-cas --resolve-special option.
|
|
... describing the recent additions.
|
|
|
|
|
|
The "generic" rules deliberately resolves conflicts on identical
paths in a latest-wins fashion (seeing all artifacts as later than
all runfiles) to allow an easy way to define actions. However, the
inputs stage obtained by this resolution can still contain conflicts
and those are an error. Properly detect those. Also clarify in the
documentation, that only conflicts on identical paths are resolved
in the described priority, not semantic overlap.
|
|
|
|
|
|
...with recent serve service fix.
While there, fix typo.
|
|
|
|
... with the main fixes included so far.
|
|
|
|
|
|
|
|
|
|
... as described in the documentation. It was never intended to have
a single string being an argument for those.
|
|
- Add missing changelog entry for 74a5fbc9644eda7f105d2d2c672a41fa5c34c6a8
- In the summary paragraph, describe what does and does not stay backwards
compatible.
- Fix typos and do proper line breaking.
|
|
|
|
Removed named keys of entries (hash, size). These prefixes were added for every chunk creating an additional overhead without any benefit.
Removed prefixes of hashes (*62*hash) appearing in native mode and creating an additional overhead as well: it is known that all of them are blobs.
|
|
|
|
Originally, the expression lanuage only contained a function to
deduplicate a list, keeping only the right-most occurence. The
reason was that this is the order needed for linking: a library
providing an open symbol has to come on the command line after the
library using that symbol (and hence making it an open symbol).
However, by now use cases have emerged that require a topological
sorting where definition comes before use; also, when composing
the value of PATH from fragments, we usually want to keep the first
occurrence in order for it to take precedence. Therefore, also
add "nub_left" as built-in function, allowing a more condense (and
slightly more efficient) description in rules instead of the
revserse-nub_right-reverse pattern.
|
|
... allowing to select only the keys in a specific subdir,
and move the them to top-level.
|
|
... and drop the corresponding design document as implemented.
|
|
|
|
... and the transition path on upgrade.
|
|
|
|
... and mention the fix in CHANGELOG.
|
|
|
|
|
|
... to report the changes so far since the last release.
|
|
|
