Hi, Quoting Sean Whitton (2016-11-13 22:37:15) > It might be nice if sbuild could run blhc(1), just like it runs lintian, > autopkgtest and piuparts.
sbuild supports running lintian, autopkgtest and piuparts because they are (or should) be applicable to *all* Debian packages. 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. So instead of adding a checker for gcc-based packages today, one for OCaml packages tomorrow and then 20 more for all the other programming languages we have in Debian, I'd rather implement support for a wrapper to these tools which is then doing the right thing. How about running check-all-the-things, for example? 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? It also supports running blhc. It also has loads of Recommends which will not get installed by the current sbuild resolver which will ignore Recommends and Suggests. On the other hand, one probably only ever wants to install a subset of these, depending on the source package at hand. blhc for example should only be installed for source packages actually making use of gcc. I wonder if there exists a heuristic to know which Recommends to be install? CC-ing pabs for advice. > deb-o-matic recently started doing this. that sounds like there is already a patch? Thanks! cheers, josch
signature.asc
Description: signature
