On Mon, 2016-11-14 at 06:40 +0100, Johannes Schauer wrote: > blhc on the other hand is only applicable for packages that run gcc at some > point during the build and will never be useful for all the other packages.
I expect blhc will work for packages that use clang too? > So instead of adding a checker for gcc-based packages today... sbuild is a tool for building packages, I don't think it should be running any QA related tools at all, unless maybe someone manually configured a hook for this. > How about running check-all-the-things, for example? See above but I mainly see cats as something to be run manually. > I do not have much experience with it, but it might be possible to > find a good way to run it as part of sbuild with the right checks? Running cats in the post-build tree is a bit rarer and noisier. > It also supports running blhc. cats currently unconditionally runs blhc on any build logs that were found. > I wonder if there exists a heuristic to know which Recommends to be install? cats will tell you at the end which commands are missing and there is a WIP branch for automatically installing the right stuff using apt, unfortunately I won't be merging that because apt build-dep installs build-essential as well as the requested packages. https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git/log/?h=wip/install The heuristics available in cats are currently only filename and mime type, as well as a way to check that commands are installed properly, for everything else you would need to insert a grep into the command. https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git/tree/data/build-logs -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
