-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove ebuilds with dead upstreams where possible #3
Comments
@awilfox has started on this arduous task, but I'm not assigning it to them. |
Yeah I don't mind contributing to this one too, as it fits with the EAPI-0 project and tree-cleaning policy which I'll try to get started on based on what's already, and continues to be, discussed. Perhaps we address this per-EAPI? ping @awilfox ? |
It's better to start with repoman and see what returns a 404 and what doesn't, then work from there. It may be useful to analyse what packages have not had commits since the git migration a year ago, also check what is m-n. |
…y David Heidelberg). Package-Manager: Portage-2.3.3, Repoman-2.3.1
…y David Heidelberg). Package-Manager: Portage-2.3.3, Repoman-2.3.1
Repoman shows a lot of ebuilds have dead upstreams (their sites 404). If the upstreams truly are dead, and nothing depends on them, they should be removed from tree.
In addition, a sweep should be checked for the last bump of the ebuild. Those not bumped for more than 2-3 years should be evaluated.
The text was updated successfully, but these errors were encountered: