This project is mirrored from https://github.com/AladW/aurutils.
Pull mirroring updated .
- Nov 26, 2024
-
-
Alad Wenter authored
-
- Oct 30, 2024
-
-
Alad Wenter authored
`build`: do not skip on partial results
-
- Oct 28, 2024
-
-
Alad Wenter authored
-
Alad Wenter authored
-
Alad Wenter authored
`Depends.pm`: remove targets recursively with prune()
-
- Oct 10, 2024
-
-
Alad Wenter authored
-
Alad Wenter authored
-
- Sep 24, 2024
-
-
Alad Wenter authored
`lib`: split to subdirectories
-
Alad Wenter authored
This commit introduces a subdirectory structure for lib. There is no effect on the installed package (the result of running the `Makefile`), and mainly serves to improve overview of the different components. Every subdirectory can have its own documentation with a `README.md` file. Every subdirectory is self-contained; any programs within only relies on programs from the same directory, or the AUR `perl` library. `aur-sync` uses programs from all subdirectories, and is thus left in the main lib directory.
- Sep 23, 2024
-
-
Alad Wenter authored
Fixes #998
-
Alad Wenter authored
Fixes #952
-
Alad Wenter authored
Fixes #1039
-
Fixes #1093
-
Alad Wenter authored
`sync`: automatic `gnupg` key retrieval
-
Alad Wenter authored
This matches the default behavior of gpg.
-
Alad Wenter authored
-
Alad Wenter authored
In certain cases, the `auto-key-retrieve` option for gpg(1) does not result in a successfully imported keys. Furthermore, this option imports (possibly unverified) keys directly into the default user keyring. Use a different approach by creating a separate keyring which is used exclusively for verifying and importing gpg(1) keys with makepkg(8) or aur-chroot(1). The keyring location defaults to `$XDG_DATA_HOME/aurutils/sync/gnupg` and can be modified through the `AUR_SYNC_GNUPGHOME` environment variable. Automatic key retrieval can be disabled with `--no-key-retrieve` / `--nokeyretrieve`.
-
Alad Wenter authored
This allows using a separate keyring for signature verification with makepkg(8) and package signing with gpg(1). The keyring location can be specified through `AUR_MAKEPKG_GNUPGHOME` in the environment, or `--makepkg-gnupghome` which takes precendence.
-
- Sep 22, 2024
-
-
Alad Wenter authored
chroot: unbreak `--path`
- Sep 12, 2024
-
-
Ivan Shapovalov authored
Avoid triggering the implied `--status` when `--path` is given. Fixes: 3c282892 ("chroot: make --status default if no modes are specified")
-
- Sep 10, 2024
-
-
Alad Wenter authored
-
- Aug 29, 2024
-
-
Alad Wenter authored
Since `aur-build` runs `aur-chroot --create` on every call, printing this becomes too chatty. Partial revert of commit 3c282892
-
Alad Wenter authored
chroot: make --status default if no modes are specified
-
Alad Wenter authored
This matches `aur-repo` behavior. In addition, if $directory/root is existing, print `there is nothing to do` with `--create`.
-
Alad Wenter authored
view: define missing XDG_CONFIG_HOME
-
Alad Wenter authored
Closes #1177
-
- Jul 23, 2024
-
-
Alad Wenter authored
-
Alad Wenter authored
perl: refactor library structure
-
Alad Wenter authored
-
Alad Wenter authored
-
Alad Wenter authored
-
Alad Wenter authored
* Move `Repo.pm` to `aur-repo-parse` * Move `Depends::vercmp` to `Vercmp.pm` * Move `Depends::solve` to `aur-depends`
-
Alad Wenter authored
* extract() -> recurse() * get() -> solve() Partial adaptation from ca8c02dd
-
Alad Wenter authored
view: set orderFile on every call
-
Alad Wenter authored
This moves the `git orderFile` logic from `aur-sync` to `aur-view`. Incidentally this was the only remaining `git` call in `aur-sync`. Calling `git config orderFile` on every `aur-view` call, instead of after a `git clone`, ensures `orderFile` always points to a valid path. For example, if `HOME=/temphome/user` aur sync ...` is run for a series of new(ly cloned) packages, subsequent calls `aur sync ...` using the default `HOME=/home/user` value would still rely on the orderFile in `/temphome/user`. This leads to errors if the path is deleted. Closes #1167
-
- Jun 30, 2024
-
-
Alad Wenter authored
repo: warn when local repo is not configured
-
Alad Wenter authored
In #1110 a mandatory check was added for the local repository to be configured in pacman.conf. However, the bulk of the aur-repo functionality is available without configuration in pacman.conf, provided the repository root (`--root`) is specified by the user.