Colin Woodbury

It looks like current Aura is not considering "provides" correctly, at least when AUR packages are concerned. This might have been broken upon the last dependency solving logic rewrite. That...

This may be a concern of `makepkg`, it's the thing that does the actual pulling of git sources. [Here's an example](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=flips-git#n14). Notice that the calling of `git clone` isn't present...

I'm going to look into `makepkg` and see if a patch is necessary there.

@Morganamilo Thanks for the link. Well the Arch devs might not like shallow cloning (they often prioritise "power user" scenarios, re: the first linked issue in the tracker), but I...

We will have to explore this as a new feature after the 4.0 release.

Official packages can be built/named however the Arch guys please. Were `gnome-autoar` an AUR package I would call that a packaging mistake. Looking at `palemoon` that's the judgment I'll have...

Ah nice edge case you've found. Yes this is reasonable - Aura would have to refilter the list of tarballs that were created in the end to only match: 1....

Thanks for the report. The dependency resolution algorithm will be getting a rewrite as I port to Rust.

While not as minimal as the output of `-Qu`, `-Au --dryrun` can display a lot of the information you're looking for.

It has been Aura policy to not manipulate the native Pacman commands (e.g. `-S`, `-Q`, etc) or add any new suboptions to them. If you like, I could add a...