Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 667876

Summary: Moving more install-qa-check.d from sys-apps/portage to the repo
Product: Gentoo Linux Reporter: Michał Górny <mgorny>
Component: Current packagesAssignee: Gentoo Quality Assurance Team <qa>
Status: CONFIRMED ---    
Severity: normal CC: dev-portage, sam
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2018-10-06 08:37:52 UTC
Now that all GLEPs are in place, I think we can start looking into moving more of Portage's QA checks to the repo.  As I see it, checks that should stay in Portage are those that either:

1. go beyond Gentoo policies and are universal enough to apply even outside Gentoo systems,

2. strongly rely on Portage internals.

All other checks (and most importantly, checks specific to Gentoo policies) should go to the repository.

Does anyone have any suggestions which checks to move, and which to keep?
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-03-04 01:52:48 UTC
I think we can do the following for sure (non-exhaustive list, but it's a good start, and the remainder we can debate/review later):
- 05double-D ("# Check for accidential install into ${D}/${D}")
- 60pngfix ("# Check for issues with PNG files")
- 60systemd ("# QA checks for systemd units.") (I don't think we can say this is generic to non-Gentoo systems, but let's skip it if it's contentious)
- 20deprecated-directories ("# Check for deprecated directories")
- 20runtime-directories ("# Check for directories that need to be created at runtime")
- 60bash-completion ("# QA checks for bash-completion files")
- 80multilib-strict ("# Strict multilib directory checks")