Age | Commit message (Collapse) | Author |
|
|
|
...as these features have already been implemented and
appropriately documented.
|
|
|
|
|
|
|
|
|
|
- For the rule functions TREE_OVERLAY and DISJOINT_TREE_OVERLAY
call the argument "$1", to align with the argument name for
BLOB and TREE.
- For the built-in functions `"tree_overlay"` and `"disjoint_tree_overlay"`,
align this the built-in function `"tree"` and allow staging of
the resulting tree.
|
|
... and remove it from the future design, as it is already implemented.
|
|
Clarify the handling and extent of proposed debug-related
configuration fields in the CC defaults.
|
|
|
|
... as it turns out that the synchronous writing is fast enough and
hence we can avoid all the problems of background processes.
|
|
Reduce interference of invocation logging with regular logging
operations; in particular, restrict just-mr passing the --async-profile
option only to build commands and thus avoiding race conditions with
calls to `analyse` that rely on having a graph available immediate
after invocation.
|
|
|
|
- specify that what is cloned is the workspace root of the target
repository
- disambiguate what is referred to as the 'start' and 'target'
repository
|
|
|
|
Marking a source repository 'as plain' means that the whole source
repository tree will get imported as a repository type
corresponding to the source type. In this case, additional pragmas
than those supported by the inndividual imports might need to be
set.
Solve this by supporting the just-mr-style 'pragma' field also in
the source description, for all sources also accepting the
'as plain' field. Currently support only the 'special' pragma.
Document change and add test for plain imports that checks this
feature.
|
|
In particular, any transitive 'file'-type repository will inherit
any given '{to_git: true}' pragma in the import description
objects. Note that this technically can only happen for transitive
'file' repositories imported from a 'file' source, so in all other
cases such a pragma would not have any effect.
Document change and extend the import from 'file' source test to
check this feature.
|
|
|
|
|
|
... rather than as future design. While there, also add target-level
caching as a service to the list of documentation pages.
|
|
The 'type' field is optional and informs both the way to unpack
the archive and which type imported file repositories should be
rewritten as in the output configuration. Mirrors the 'just-mr'
types, with options for tarballs and zip-like archives, defaulting
to tarballs if missing.
The 'mirrors' field is treated the same as for 'git' sources.
The 'subdir' field is optional and accounts for the fact that the
actual root of the source repository might be a subpath in the
unpacked archive, as opposed to Git repositories where it is
reasonable to expect that the sources root is the top-level
directory.
|
|
...to refer to repositories as a chain of bindings to be followed
starting from one of the known repositories (existing or imported).
Both the initial and the target repositories are to be kept during
deduplication.
|
|
|
|
|
|
|
|
... specifically for the use case of target files depending on the
directory structure.
|
|
... and drop the corresponding design document as implemented.
|
|
directory
... instead of always having to execute actions in the top-level directory.
|
|
|
|
... and mention the fix in CHANGELOG.
|
|
|
|
|
|
|
|
|
|
... and document the implementation in the concepts documentation.
|
|
|
|
The base functionality is already implemented. Also, the default has
changed with respect to the design to make reading symlinks the default
and only follow symlinks if the optin --follow-symlinks is given.
|
|
... to clean up what can be done without losing cache information.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The implicit extensional projection of target-level caching and
garbage collection interact in a subtile way. Add a design document
describing how we keep the invariant required by target-level
caching in the presence of garbage collection. While, techincally,
this just describes how to fix a bug, a careful design is still
needed, as some fundamental changes are made.
|
|
|
|
|
|
|
|
|
|
|