Alad Wenter

`chroot`: replace devtools functionality (part II)

2

Follow-up to #1155.

This moves the `pacman` database synchronization to a helper script `aur-build--sync`, which can be run independently. * The proposed implementation uses `pacsync` / `pactrans` with a temporary pacman configuration file....

`pacman` prompts cannot be answered

5

Case in point: ``` % aura -A aurutils aura :: Determining dependencies... aura :: Repository dependencies: aurutils aura :: AUR packages: aura :: Proceed? [Y/n] y resolving dependencies... looking for...

`sync--filter`: improve diagnostics for package removal

1

It's sometimes not immediately clear why `sync--filter` removes packages from the queue. Diagnostics could be added to improve this, e.g. `package in local repository`. Comparison: messages in `repo-filter`.

`examples`: use `ysh`

1

`ysh` provides benefits of both command languages (bash) and scripting languages (python, perl, ...). This helps with scripts like `examples/sync-rebuild` that use Python for convenience but mess about with `subprocess`...

`pactrans` defaults to `--spec` for installing package specs. `build--sync` runs it without arguments, expecting an `-Syu`-like operation on the local repository. Without appending `--sysupgrade`, `pactrans` then errors with `error: no...

workflows: add regression tests

1

Is this going to hit the time limit? Fixes #1231

To avoid issues like #1230.

On `sudoers` rules for commands vs. scripts

3

For running commands such as `pacman` and `pacsync`, there are two approaches: ---- Run every necessary elevated command inside an aurutils script, for example ```bash argv0=build--sync ... $AUR_PACMAN_AUTH pacsync ......

When the caching interval (for sudo or other elevation tools) is set sufficiently low, there are up to 4 elevation prompts. Elevate to root when any privileged operation is required,...