On 09/07, Nowaker wrote:
Maybe there should be an auto-orphan feature after x days/weeks if the package was out-of-date or being flagged for broken y times.
Just reported https://bugs.archlinux.org/task/41140 Reference: https://mailman.archlinux.org/pipermail/aur-general/2014-May/028506.html
Regarding out-of-date (not updated to the latest version), broken (build fails), incomplete (no systemd units), bad name (should be ruby-blah not rubyblah) or whatever else can be invented. The package needs to be updated no matter the reason for being flagged - thus, auto-orphaned so interested people can take care of it. Therefore I don't think differentiating between out-of-date, broken or whatever is useful for anything.
The problem is that sometimes a package is out-of-date but can't be updated for various reasons. Like the openhexagon package, it's pretty much impossible to build it from scratch without replacing the build system with doing it manually in the PKGBUILD, and in the binary package of the new version there's tonnes of broken symlinks and weird conflicting files. (Someone complained about not being able to run it, he responded by copying the contents of his /usr/lib into the package.) I've tried to get it working properly, but it seem pretty much impossible. I've also tried to talk to upstream, but his answers basicaly came down to "I don't know cmake properly" and seems to have no intention of actually learning or listening. -- Sincerely, Johannes Löthberg PGP Key ID: 3A9D0BB5