Hi, Quoting Paul Wise (2016-11-14 07:55:59) > I expect blhc will work for packages that use clang too?
maybe. The man page says "Only gcc is detected as compiler at the moment". > > 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. Yes. That's why the existing lintian, autopkgtest and piuparts checkers are disabled by default. > > How about running check-all-the-things, for example? > > See above but I mainly see cats as something to be run manually. What is "cats"? If it's check-all-the-things, then I don't see what the "s" is doing at the end. > 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 As far as sbuild is concerned, it doesn't need check-all-the-things to call apt itself. It would be sufficient if check-all-the-things would somehow produce a list of binary packages that sbuild will then install using whatever resolver the user selected. Thanks! cheers, josch
signature.asc
Description: signature
