Age | Commit message (Collapse) | Author |
|
FossilOrigin-Name: 1f4476fd14406be62ea7a09a9ea0f6cc04907b6eeecbd991396cb91f9e5e96dd
|
|
FossilOrigin-Name: 2ded60ede324d5b94db96a5267b22263281e611b1662f327c31da3c21b6acf48
|
|
FossilOrigin-Name: 7f6535ab78b05c31f751fa763ff988ace8d4c6bda99fddeb2bc7638e2c07d221
|
|
FossilOrigin-Name: c0bbaed4949169d212ece054db5c9f278abb57f1242043bcb18409a286e3cb45
|
|
FossilOrigin-Name: 1139782a2f958ea86a02eb3b252c8fc8fe75786510ef73e65d9e03eb5d4a2f44
|
|
FossilOrigin-Name: 6e5c41e40438e00decab65e1dcbb577274f06069ba2b8dd5b4d124cd6dc2880b
|
|
FossilOrigin-Name: 2aaf44b696b5d66754f9886c20e9f705ae736213c8daa63e55620f239b0a92ef
|
|
FossilOrigin-Name: 5c9058614a2b092590fe45fd58017f87a3cd995a32fbc56640c5ce99438501f1
|
|
FossilOrigin-Name: 83ae4a759534bb013b2b6c3db11874017869e70c7566f89dc6a86a0b2c4c6df3
|
|
FossilOrigin-Name: 02afaeacc5979da2b39da26aa7e0145f4d120cbddfeaa4bfc8060c319c85b672
|
|
FossilOrigin-Name: 69c1bc599a5f6e9127ac31af9c8334d427b52746d0c10723fe4938b443c3d158
|
|
FossilOrigin-Name: 541a3f8b59bda394154164db7901e8957d578a543ab020b29b71f14de5d13886
|
|
FossilOrigin-Name: 75d3b93e2d6d4a8e7a5b0d5e36a68289c7923ecff4140784363a3e78a068ec02
|
|
FossilOrigin-Name: 51658a4ad9ab409e8cc776d2640cb2eb6da420ea0791f071142afb0a588b67d2
|
|
FossilOrigin-Name: 5e436d4946dc736529a60834f37cc6055a7ad672de30c1f347e22ef0e3bb1107
|
|
The substitution we used on pax didn't exactly match the behaviour of
tar implementations that supported `--strip-components`. This change
makes sure that we actually DO strip a component no matter what and we
don't have inconsistencies between the choices we deliver.
FossilOrigin-Name: 3c2771c89e72ef79de6aa0d1f53ad1bf3a11b654e022ee5c5d0761da01e1c335
|
|
sbase utilities don't accept flags after arguments begin, meaning that
the '--' is accepted as an argument instead of the "end flag", which
causes the utility to fail because it looks for a file named '--'.
FossilOrigin-Name: 29dc20b69d0e93cc8a4a52601745135911e7f396d25bf5653728efc88025f775
|
|
FossilOrigin-Name: d184f8e784279a92746e9de38b1b2c7359534204ed0f75575a07ddac3fbac4e8
|
|
FossilOrigin-Name: 6ffa441f3ea44d7176fd45de239f0f54ac2175f1e17b6d6419579a2d5c2cbc98
|
|
FossilOrigin-Name: 422290edbd1d0c1cf98ae3d239f49c901eadf736f957bf1328df939de2cc9f63
|
|
FossilOrigin-Name: 3b5c37511a3cc0e5164844a08e64af2b8e39f578e8d31e23f3d5c183ecefa40d
|
|
FossilOrigin-Name: 393a3a3099894625cffeec866889b3534b8b1d8866f4d967a73f3986101c55a4
|
|
FossilOrigin-Name: 7cd4336b0ea7c9571aa6c843afb3efdec5677f0d10d939ede95bacb9a0ed2fac
|
|
FossilOrigin-Name: 36c7a2c98510370887251c35cc19e7c1a42893d12677fe9c1a93b541d9d56b1c
|
|
See https://github.com/illiliti/ssu/issues/2
sls is moved to the end of preference order, and will be removed at the
end of May. A deprecation notice is printed every time as_root is called
with sls.
FossilOrigin-Name: aedab01c988ac2f25014c27e776075288f97b2083b5b06d500673cc2ae62a193
|
|
FossilOrigin-Name: 1cb9a4e4a9b69ba0dd91f48ff1100587dc6ffb9b9fed7e060f838672f1294473
|
|
FossilOrigin-Name: 240daa9617936e7676d568290a1660a01262ec50571d7431b1ca60735aab6634
|
|
FossilOrigin-Name: 048c099fa4155f31725c51c27b09359d7b04f4c2d7e64f2a2b381ab7dea7803d
|
|
Even though we had a portable extraction method for tarballs, this slowed
down the extraction immensely. I have added 2 new methods for tarball
extraction so that we have faster extraction speeds based on the system
tar implementation. Here are the options with the order of preference:
- pax: Although an uncommon program, pax is defined by POSIX, and
supports regular expressions, meaning that we can 'strip' components.
This is slightly faster than bsdtar and GNU tar.
- bsdtar/gnutar: We simply use '--strip-components 1' for these tar
implementations.
- tar: This is the portable method we had been using for a while, it's
good, gets the job done, but it is slower.
Here is also a little benchmarking I did by extracting the Linux tarball
for 10 times per method.
tarball=$CPT_CACHE/sources/linux-headers/linux-5.10.12.tar.xz
for extract in pax bsdtar tar; do
time sh -c ". cpt-lib
extract=$extract
for i in \$(seq 10); do
mkdir -p hdr; cd hdr;
tar_extract \"$tarball\"; cd ..;
rm -rf hdr
done"
done
This yields the following output, methods are as ordered above:
sh -c 75.21s user 11.11s system 115% cpu 1:14.90 total
sh -c 78.68s user 14.64s system 124% cpu 1:15.15 total
sh -c 99.88s user 69.99s system 119% cpu 2:21.70 total
FossilOrigin-Name: 45e3a9a03e7eff9b30b0e911d68d44068e8681ebf4501f271c8a686118f29243
|
|
FossilOrigin-Name: ff26aa326167c4751040d86e06e298ac11b4ed7923b729ed3940e881bdc24124
|
|
FossilOrigin-Name: 536a4979e768c7b605a393251f0468a878e46a23b554045049b7404072b5258b
|
|
FossilOrigin-Name: a7f5ddfe5f7fdc9ea329ed8175c3ad237e7a7460bcbb3de4855d2af3f233176b
|
|
This ensures that we create the needed directories regardless of pkg_extract()
FossilOrigin-Name: c7c7c11246aeb74343f06e1d5d53ea9ad4cab2f4153d745cb00ae0c62f51b048
|
|
FossilOrigin-Name: a77a19063999297dfeb45dd725cb78dea0482030571dba0a34ae79b02e1c99fd
|
|
FossilOrigin-Name: 4bd8dc7830c8308c31510e5624550b1cf39df1401b4091a5bb80a2e24e109a30
|
|
FossilOrigin-Name: aae19d6384369835236023c30bfb54d24e9bf4021ff8d6fa10dbed8611419229
|
|
FossilOrigin-Name: 81b5d4e8c446aa4e4df789882bb5900d9636f4e5f6e9206e01ed42dfce946ad0
|
|
FossilOrigin-Name: ec9c5047e0bd1ef84104e66206db9a44e1b1e519f60519011c92b5c4e8e03657
|
|
FossilOrigin-Name: 035deb0250c22e7feafad486f8f2b1a40893ad87073c8e41ba4bdc0db0d23d62
|
|
This bug caused swapping prefix files to malfunction on manifest files.
Example:
swapping redo caused redo-* files to be swapped on the manifest with the
name 'redo' without actually moving the files to the alternatives
directory either.
FossilOrigin-Name: 5966d079397154246173b94f53de83212c20edeb53f75089092cec352e6316f4
|
|
Just so you know, the error is due to a bug on the older versions, but
we still don't want checks to fail because of it. Installing newer
versions of shellcheck takes too long on test containers that I am okay
with fixing a faulty error.
FossilOrigin-Name: 179ced7baf35e7eace835e1f7903ce72d2249e7ec6c809cfdd92ba7aa14b2517
|
|
FossilOrigin-Name: cc958373d206ec3dd65008461a715120b25f05772b9a2d70539b3a53839569c2
|
|
FossilOrigin-Name: e56971ac89f4a4e1c3efd62dad13b3a1c43bc6266c2803600995954cb61ee6cd
|
|
FossilOrigin-Name: f282158e981153846bc1aca83263de583403dd78444435cb139a7f25e6658c4e
|
|
FossilOrigin-Name: 3c44de3bfd6fbf69658371b2d8cd4d30043dd6f9b568c43ab30291925ebc582e
|
|
FossilOrigin-Name: e512f7d12e12c16fe109cfdf642361bb46ba594273ecacd93531c0ddfb144a8e
|
|
FossilOrigin-Name: ca05dfca6f8529b23647ddac4e9d7d3317c4508ee15045e60a4eac63787a04b7
|
|
FossilOrigin-Name: 47fe062d11c48e1cc51d6a2a4d6e3e4d54524e27281dc18ef69ec71f3bd9bcb4
|
|
FossilOrigin-Name: e34f2e3bf42cdfa6bdc94ffafbf1c7d58bc2a377608549e70c7b8bc426592272
|
|
Using awk, we can achieve the following things:
- Ignore the rest of the file (2 times faster than sed)
- If the line doesn't match the docstring pattern, we can just print a
newline instead.
I am not exactly really familiar with awk scripting so there might be a
better way of doing this. In that case please send a patch and I will
apply it.
FossilOrigin-Name: bf65db74ad6552bb374f3535ef2a5333bbc0dc3d20563ec37e821036e07f621f
|