Rich Freeman schrieb:
You say that there are no bugs in those packages. How do you know? You don't know unless you test it, and no maintainer means nobody is known to test it regularly. The package can be pretty much completely broken and we'll not know unless someone tests it.This sounds like a tree falling in the forest with nobody around... If a package is in the tree, and it has no known bugs, and no users, who cares? If somebody tries to use it, and it doesn't work, then they can file a bug, and then we can treeclean it.
One might add here that toralf is doing a great job at building all packages and reporting those that fail. So at least we see build failures.
Having a graveyard that ONLY contains broken stuff as an overlay just doesn't make sense to me. Why would you install packages directly from it without fixing them first? Certainly for build failures you'd be forced to do this. I guess for security issues you could decide that you don't care, or that your host is in a locked room with no network access or something. However, these seem like such minor use cases that somebody could just stick the ebuilds in their own overlay if they needed them.
I think the point of a graveyard repository is that discovering and extracting deleted ebuilds from git is more cumbersome than from CVS attic.
It would be even better if the graveyard repository preserved the commit history, but I don't see any easy solution for that.
Best regards, Chí-Thanh Christopher Nguyễn
signature.asc
Description: OpenPGP digital signature
