Age | Commit message (Collapse) | Author |
|
... and extend compatibility by not relying on arguments
that are only supported by GNU patch implementations.
|
|
... because it was using tool that are not part of
coreutils. Using patch parts can still be done via patching
patches.
|
|
... instead of creating an ENV from it and propagating this.
The idea is to keep PATH entries separate and only join them
with ":" when we need it. In this way, we can accumulate
PATHs from multiple defaults later, and perform a
deduplication ("nub_left") to shorten the final string
length.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Similarly to tarballs, an autodetection option for zip-like
archives is added to enable a unified handling of both traditional
zip and 7zip formats. Thus, for "zip" archives just-mr uses now
this autodetection option.
|
|
Also updates the archive usage tests accordingly.
|
|
|
|
These are provided by the recently added liblzma external dependency.
|
|
We shouldn't exclude the possibility of receiving uncompressed
tarballs as repositories in just-mr. Therefore, we introduce an
explicit type that performs the autodetection (default behaviour
in just-mr). This is done to also be more in line with our
implementation which allows the granular handling of various
archive types (currently used only for testing purposes).
|
|
Tests for various archive types are by design repetitive and thus
can be streamlined to avoid excessive code duplication. As a
positive consequence, this change also adds previously missing .xz
archive usage checks.
|
|
|
|
|
|
While a foldl is enough to implement a reverse functionality,
adding it as a built in allows doing so in linear time.
|
|
... to obtain from a list of strings a map with those entries
as keys and true as value. In this way, repeated membership tests
in lists can be implemented more efficiently.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
... also verifying that we can look into tree outputs
|
|
|
|
... in order to make that functionality reusable
|
|
|
|
|
|
The rule generates a non-upwards symbolic link with given target
path.
|
|
|
|
Verify that install and install-cas do not overwrite and instead
replace existing files. This behaviour is less surprising for the
user in the presence of hard links.
|
|
If install-cas finds a file in the target location, unlink it before
writing (in the same way as install does already). In this way, we
avoid changing other file locations in the presence of hard links.
|
|
|
|
Due to a possible clang issue, protobuf v23.4 fails on debian-12
built with c++20. As such, protobuf and its consumer grpc have
been set to build with c++17 until this is resolved upstream.
Co-authored: Paul Cristian Sarbu <paul.cristian.sarbu@huawei.com>
|
|
|
|
This corresponds to the highest current version found in popular
distros (in this case, the one in Arch Linux).
The abseil library is now a dependency of protobuf (for logging).
|
|
Also adds the extra targets needed by protobuf v23.4, which now has
a dependency on abseil, and by grpc v1.56.2.
|
|
|
|
Upwards symlinks should still be collected from actions, even if
only the non-upwards symlinks are supported artifact types. The
client side is thus the one responsible with enforcing the
non-upwardness condition.
|
|
|
|
We now allow restrictive use of upwards symbolic links when
importing filesystem directories and archives to git.
|
|
Checks that the new 'special' pragma works for all supported
repository types. In particular, checks that symlinks get resolved
as expected and that resolved trees add their unresolved
counterparts to the CAS for 'file' and 'archive' type repositories.
Splits install-roots test into a basic check which works with the
bootstrappable just-mr, and a new check focusing on the newly
introduced 'special' pragma.
|