AUR registration disabled
https://lists.archlinux.org/archives/list/[email protected]/thread/4JRS73YVTE7JUYHHE3ZDUIHXYHXZ3YQQ/
AUR registration disabled
https://lists.archlinux.org/archives/list/[email protected]/thread/4JRS73YVTE7JUYHHE3ZDUIHXYHXZ3YQQ/
realistically the problem is only with abandoned packages. compare it with with debian where they're semi-automatically scheduled for removal
so what do you do instead? "curl | bash"?
@mattesilver Nope, never. Though I was not affected by the AUR hack, I have lost trust in it. I had nothing critical from the AUR that I urgently needed, so I removed all AUR packages. Currently, I only use what is available in the official Arch repositories.
If I ever need something from the AUR, I will download the PKGBUILD manually, review it, makepkg --verifysource, and build it with makepkg.
> I have lost trust in it [...]
The AUR shouldn't be (blindly) trusted anyway, so good :)
> If I ever need something from the AUR [...]
You're basically describing the normal / expected and officially documented way to install packages from the AUR (https://wiki.archlinux.org/title/Arch_User_Repository#Installing_and_upgrading_packages). AUR helpers (or any other way to interact with the AUR) always have been discouraged and unsupported.