Alad Wenter

Simple solution: bump the RPC version to 6. People who want the old API can keep using 5.

Made its way into v11: https://github.com/AladW/aurutils/releases/tag/11

It took a rewrite in `perl` to solve this fully: https://github.com/AladW/aurutils/pull/1041 Any `provides` specified on the command-line are used transparently. `--table` also adds a `Self` line for any target mentioned...

> Note that https://github.com/AladW/aurutils/pull/1041 does not update aur-sync to account for aur-depends changes yet. This should be a routine change though. This was also implemented in #1041

> build should probably be able to find since it's available on the AUR. `build` doesn't do AUR dependency resolution, you need `sync` or `depends` for this. Anyway `cpu-x` does...

Here's a prototype using author files. I didn't look into `userdata` yet. Instead of retrieving the maintainer name from aurweb, I opted to look at the git commiter. This also...

As outlined above, this could be used to set up a simple "trust system": ```bash #!/bin/bash argv0=view-maintainer-change trust_list=$XDG_CONFIG_HOME/aurutils/view/trusted # Set up list of trusted author name/emails declare -A trust_list while...

As mentioned on IRC, the above is not sufficient - any maintainer can use any git author/commiter name and email. edit: ``` another problem: there is no exact match between...

Right, but there is no way to map AUR (co-)maintainers to whoever pushed the commit. A series of co-maintainers might even push commits under the same common email, e.g. for...

This should be covered by the new dependency code (`Depends.pm`), specifically `Depends::prune` which does a kind of reference counting.