Alad Wenter
Alad Wenter
Going over `aurvcs.7` makes me wonder why `aur-srcver` makes any attempts to limit effects of sourcing PKGBUILDs, when it runs `makepkg` anyway... and `libmakepkg` functions could be called instead. e.g....
Another observation is that `aur-srcver` can't take input from `stdin`. I guess this was an oversight when migrating scripts to use `-`.
One detail is that `pacman -Syu` commands in `aur-build` are always elevated with `sudo`. With a user-writable `--dbpath`, this is however not necessary. The elevation command could be exposed through...
The commit in question, as mentioned on IRC: https://gitlab.archlinux.org/pacman/pacman/-/commit/2535611d6c3cbf951408c50ab35953efaf32f686
This seems less useful than it could be, because `makepkg` has no way to pass on `--dbpath` to pacman. Even if a wrapper is used, the lock file is fixed...
`PACMAN_AUTH` was implemented with #896 Specifically, `PACMAN_AUTH=fakeroot` can be used with a user-writable `--dbpath`.
I suspect in 2.x `aur build -c --pkgver` would install the `makedepends` both on the host and in the container?
May be related to not using `--noprepare` then: ad7055b7a19a03a92c027407b0301ee143e7f116
As far as I know `bauerbill` and `aurto` have this implemented in some way. I didn't check in what way though.
Note you can also just subscribe to email notifications for the packages you use (I guess this only scales to a certain amount of packages). One approach is to save...