[Soc-coordination] Fourth report: Provide some metrics in Debile

[Clément Schreiner]

Hi,

this is the fourth weekly report on my Summer of Code project 'Provide
some metrics in Debile'[1]. 

(Previous report:
[http://lists.alioth.debian.org/pipermail/soc-coordination/2014-June/002077.html])

scan-build/clanganalyzer
------------------------

Léo's clanganalyzer plugin is now working. However, some packages do not
honor the CC et CXX environment variables, and the plugin's hack does
not work with them.

It might not be realistic to make all C/C++ packages honor them, so
another strategy might be needed, to force them using clang
anyway. Sylvestre suggested using ccache's mechanism for that.

building NEW packages and full-rebuild of the debian archive
------------------------------------------------------------

I have begun packaging ricky[2], loofah[3] and fred[4], so that we can
rebuild all packages (with loofah) and automatically build NEW packages
(with fred).

I have a first draft on a package for ricky[5], and it seems to build
correctly[6]. However, it has lintian errors, and I haven't tested it
yet.  I will fix that shortly, and then do the same with loofah and
fred, and I'll set them up on ursae (debile.d.n).

next steps
----------

Now that I've almost finished setting debile up on the new servers, I've
spent some time thinking about what I should do now.

 - I still need to improve debile-incoming's performances

 - I'd like to add a new check to debile, using Sylvestre's script that
   detects if a package honors the CC and CXX variables. I'd then
   improve debile-web so that we can make sense of the data.
   
    + plug firewoes[7] into debile-web, enabling an user-friendly
   interface to firehose[8] files

    + start working on a check-centered view, allowing to see which
   packages fail or do not fail the checks.

    + find a way to filter these results by the languages used by the
   packages. Indeed, it doesn't really matter if a python or haskell
   package doesn't honor those environment variables, since they are not
   used for their building.

 This way, I can start working on the actual GSoC project with a task
that will help improving another part of debile, the clanganalyzer
check, either by determining which packages need to be fixed, or by
helping choose another strategy for the clanganalyzer plugin


Thanks for reading,

-------
Clément


[1] [https://wiki.debian.org/SummerOfCode2014/StudentApplications/ClementSchreiner]
[2] [https://github.com/paultag/ricky]
[3] [https://github.com/paultag/loofah]
[4] [https://github.com/paultag/fred]
[5] [https://mentors.debian.net/package/ricky]
[6]
[http://ursae.inria.fr/debile/files/default/ricky_0.1-1/build_all/285/ricky_0.1-1_all.6.log]
[7] [https://github.com/Debian/firewoes]
[8] [https://github.com/fedora-static-analysis/firehose]