I sometimes do report messages like : * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. * xxx * Please do not file a Gentoo bug and instead report the above QA * issues directly to the upstream developers of this software. * Homepage: http://x.y.z to the appropriate sides. It least one time a dev was annoyed by the word "poor", maybe we can lower the message to something like : QA Notice: Package may compile fine but may exhibit random runtime failures. ? Reproducible: Always
(In reply to comment #0) > It least one time a dev was annoyed by the word If they take offense to that then they're too sensitive. I think "poor programming practices" is a reasonable way to describe it. Maybe "questionable programming practices" would be a less harsh way of putting it.
i might be reaching, but i think there are cases where the code builds fine, but then an external library changes, and what used to compile cleanly now has warnings and hits the warning in question. and even if developers have sh*tty practices, they dont like being told so. telling them the blunt truth doesnt gain us, but perhaps slightly more "PC" wording will ? (yes, i know i'm the source of the original language, and the intended target was people with sh*tty practices, but some people simply arent aware ...)
(In reply to comment #2) (yes, i know i'm the source of the original language ...) Does this mean it is up to you to change that ?
I've fixed it to refer to "severe warnings" instead of "poor programming": http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=62da1be30a7b9a9d550e63a18f0c6736f0801b59
This is fixed in 2.1.10.19 and 2.2.0_alpha59.
Although it might be OT here this link http://bugs.ghostscript.com/show_bug.cgi?id=692515 is a current example that this feature is useful :-)
