| commit | eb37ef9672b0b25413552a293dadc99c4f1d7ae1 | |
| author | Alad Wenter <alad@archlinux.org> | |
| Mon, 17 Apr 2023 13:26:16 +0000 (17 15:26 +0200) | ||
| committer | Alad Wenter <alad@archlinux.org> | |
| Mon, 17 Apr 2023 13:26:16 +0000 (17 15:26 +0200) | ||
| tree | 0a8340521191279a67280e67b6be608cac9eef8d | treesnapshot (tar.gz zip) |
| parent | dc815835030e48f7b486812f4b0807eaf177363a | commitdiff |
sync: revert 423ab2f61b410c3e46451b01913f9cd6b4f2d82c
Using the chroot path for `repo-filter --sysroot` has two limitations:
* If the chroot was not created (`aur chroot --create` or `aur build
--chroot`) before `aur-sync` is run, an error message appears;
* `repo-filter --sysroot` is run before `aur-build`, specifically before new
pacman databases are pulled to the container with `pacman -Syu`.
This is an inherent limitation with seperating fetch/repo-filter from aur-build
in aur-sync. The chroot create/upgrade step could however be moved to `aur-sync`
in a later commit, with `aur-build` optionally not running this step by default.
Using the chroot path for `repo-filter --sysroot` has two limitations:
* If the chroot was not created (`aur chroot --create` or `aur build
--chroot`) before `aur-sync` is run, an error message appears;
* `repo-filter --sysroot` is run before `aur-build`, specifically before new
pacman databases are pulled to the container with `pacman -Syu`.
This is an inherent limitation with seperating fetch/repo-filter from aur-build
in aur-sync. The chroot create/upgrade step could however be moved to `aur-sync`
in a later commit, with `aur-build` optionally not running this step by default.
| lib/aur-sync | diffblobblamehistory |