Colin Woodbury
Colin Woodbury
Yes by default if a particular package is found in both some prebuilt repo and the AUR, the prebuilt one will be installed. I'll see what I can do about...
It wouldn't surprise me if these are side-effects of the latest patch. One other thing to try is to specify an alternate build directory with `--build=/full/path/to/build/dir` which could be, say,...
Yes that would work well too. Whatever is well understood and easy for users to clear if they need.
Either `/etc/aura.conf` or `/home/you/.config/aura/aura.conf`. I know you build from source, but otherwise you could `man aura.conf` for more info. Here's a template: https://github.com/fosskers/aura/blob/master/aura/doc/aura.conf
> Incidentally, how would I build aura with stack and get the docs (man page)? Unfortunately there is no such official way, unless you install via `aura-git` as you mentioned....
This is the same strategy I myself use when testing the completions.
Aura piggybacks on the Pacman database for all things related to actual installation of packages. In `alpm.h` we find the following install reasons: ```c /** Package install reasons. */ typedef...
Do you mean extending the `_alpm_pkgreason_t` enum? That would indeed be breaking in a number of places, since a number of places in their code assumes a reason of only...
I'm trying it on my own machine, and `--force` does work. Try watching the `makepkg` output with `-Ax`.
Correct. Note that you can change the default VCS build path with: ``` vcspath = /var/cache/aura/vcs ``` in `aura.conf`.