Summary: | New QA warning for mislocated app-defaults files/directories (Feature request) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Samuli Suominen (RETIRED) <ssuominen> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | x11 |
Priority: | High | Keywords: | NeedPatch |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Samuli Suominen (RETIRED)
2009-08-09 07:41:15 UTC
How about something a bit more abstract. Basically have a 'path inspector' function. This could be python, or it could be a bash function from profile.bashrc (so we keep as much QA code outside of portage as we can) and this inspector function basically gets called after src_install or possibly after postinst (so the postinst doesn't screw with the paths or we don't scan things that get deleted?). We can call it once per file (probably expensive) or better yet call it in batches (don't want to hit the ARGV limit). I don't like QA code in portage because while Zac can basically release portage versions relatively quickly he can't make developers upgrade to the new releases so older versions can contain QA-code bugs and then get angry at false positives, false negatives; if we continue to write QA code that ships with Gentoo-x86 fixing it once fixes it everywhere (alternatively; breaking it once also breaks it everywhere; but I assume it will be fixed relatively quickly.) Looks like this is a duplicate of bug 273282 in fact. *** This bug has been marked as a duplicate of bug 273282 *** |