You are not logged in.
Approximately 13% of AUR packages are orphans. There are literally thousands of packages that have not been touched in the last 5 years, probably they cannot currently be built or they are not used by anyone. I don't think this is a good thing and inspires much trust.
In my opinion AUR should automatically remove packages that have been orphaned for 2 years. What do you think?
Excuse my poor English.
Offline
Nope.
Perhaps if they are orphaned and they won't build. But I assert, without proof, there are many useful, unmaintained packages that continue to build just fine.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
I'm more concerned with the bots that spam the aur with literally hundreds of broken packages. They all show as actively maintained, but they're garbage. I've reported a couple such packages as they affected me in some way - and those packages may be removed, but the bot users are left to go on spamming new garbage packages unchecked.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I'd disagree. AUR packages aren't trusted by definition so you should know what you sign up for regardless of how maintained something is. And if I run into a tool I want to try out and there's already a PKGBUILD it might be easier to patch it up with a PKGBUILD already present for reference.
Offline
In 2015 AUR switched from version3 (tarballs) to version 4 (git-based ) . In order to get a fresh start aur3 was archived and maintainers had to do a fresh upload to get packages in aur4
The aur3 archive is still available on github .
Maybe a similar cleanup would be a good idea ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
So we're poking people in the eye to see whether they're still alive?
The 2015 incident had a technical background that was used to clean up, but "because we can" is no justification to bug people.
Also
There are literally thousands of packages that have not been touched in the last 5 years, probably they cannot currently be built or they are not used by anyone.
is based on feelings?
There's useful upstream code that hasn't been touched in over two decades - that doesn't mean it doesn't build or is not used. Just that there's no need for change. What about font/artwork packages? Do we expect them to be cfrequently updated? Git packages?
Afaics one either runs a conclusive test over the AUR and builds everything to see whether there're issues, ping the maintainers and then act on silence or relies on users strolling along and reporting the package as broken.
I don't think this is a good thing and inspires much trust.
Trust in what?
As V1del pointed out, if one trusts AUR packages, one does it wrong.
Offline