Colin Woodbury

_Please finish this someday._ :laughing:

I have considered in the past having Aura do shallow clones of any package it needs during the installation process, and pulling metadata from that. Kind of like how Pacman...

Right, it wouldn't. You'd basically have to do what aurweb already does, but locally, keeping a managed database of what split packages belonged to what package base. Probably out-of-scope for...

Thanks for reporting this, I've been noticing this too. For now you can pass `--nocheck` to make Aura's inner `makepkg` call avoid running the `check()` function (and thus those dependencies...

The `-h` output of the current Aura `3.x` series is one of the things I dislike most about it, but luckily this problem is already solved in the on-going [Rust...

You're right that Aura hasn't ever accounted for what's currently in the AUR when checking for Orphans. It's local definition of orphan is what you've stated: a package that has...

I like the idea. It could potentially live under `aura check` (a new feature of the Rust port), although that's more for verifying your system setup as a whole. Perhaps...

Yes I am, so long as the changes are minimal. I still have a massive TODO list on my own end, and things are likely to change. So I'd say...

I suspect this is due to Aura `su`ing back down into the build user during actual building. When it does this, it looses the environment variables that were passed through...

At earliest I could see it being done in a month with the new schedule that I have.