I would like to reopen the discussion to delete a package (yuzu-mainline-bin) that exists in [community] (yuzu).
As per AUR guidelines [1]:

>The submitted PKGBUILDs must not build applications already in any of
>the official binary repositories under any circumstances. Check the
>official package database for the package. If any version of it exists,
>do not submit the package. If the official package is out-of-date, flag
>it as such. If the official package is broken or is lacking a feature,
>then please file a bug report.
>
>Exception to this strict rule may only be packages having extra
>features enabled and/or patches in comparison to the official ones. In
>such an occasion the pkgname should be different to express that
>difference. For example, a package for GNU screen containing the
>sidebar patch could be named screen-sidebar. Additionally the
>provides=('screen') array should be used in order to avoid conflicts
>with the official package.

yuzu-mainline-bin provides zero extra features or functionality compared to
the repo build, at least, no one has yet mentioned such.
The name itself refers to yuzu-mainline which is exactly what the repo package is building.

As a result I filed a deletion request, but this was apparently rejected [2] with the reasoning that
"Yuzu only seems to support binaries", along with some links to comments from upstream as
well as a link to a previous thread [3] on the ML from 2021 where this topic was mentioned before.

The other point mentioned in the AUR package comments [4] is that the repo version can be out of date frequently.
Again, that is addressed in the quote above, still doesn't justify the AUR package.

To me, the entire purpose of having the official repos is to have binary builds (presumably done
in a clean environment with some minimal source verification), so we don't have to rely on arbitrary
developers to have clean environments and only really need to trust the TUs who build that package.

If there are issues with a package, they are first reported to Arch maintainers via bug
report (this is in accordance with the "please file a bug report" in the quoted passage above).
This applies to any package, and yuzu is neither an exception nor special case here.

Also the entire point of having distros in the first place is that you have someone
(who is usually not upstream) maintaining the package and making sure it slots well into your system.

I don't know of any package in any distro where the distro builds the package, but upstream is expected to support it.

So why should a specific -bin package exist in the AUR just because upstream is in accordance with decades of tradition?
Either way they clearly do not want unnecessary bug reports from inexperienced users [5], so any Arch user
reporting a bug with the repo package upstream would be unhelpful to both Arch and Yuzu.

Best,
éclairevoyant

[1] https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submission
[2] https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/message/GJWE3A6IMN2XFW4VFC4BNG3N2BXIOWO5/
[3] https://lists.archlinux.org/pipermail/aur-dev/2021-December/005056.html
[4] https://aur.archlinux.org/packages/yuzu-mainline-bin#comment-913540
[5] https://github.com/yuzu-emu/yuzu/blob/master/.github/ISSUE_TEMPLATE/bug_report.yml?plain=1#L6