Dennis Peterson wrote: > Török Edwin wrote: >> The problem is that the output from ./configure is lost after you >> install ClamAV. > > That is absurd. > > ./configure |tee config.rpt > >> On 2009-03-02 01:41, Dennis Peterson wrote: >>> but the objective of summaries is to >>> provide self-help for non-expert implementers. I like it because I do a lot >>> of >>> telephone and email technical support and these summaries and reports from >>> tools >>> like clamconf and postconf (Postfix) are excellent assets. And I don't see >>> a >>> downside. >> Yes, I think this feature belongs to clamconf. >> It already reports your configuration, it could also report missing >> features, and their reasos; grouped by their severity: >> first features that are needed to take full advantage of the engine >> (like bzip2, and unrar support), and then features >> that are not essential for clamav to function (memory-pool, clamdtop, >> clamav-milter, etc.). > > Clamconf is a marvelous tool but useless until after clamav is built. We're > talking about that period of time prior to a successful build.
It's not too complicated to implement the idea. At configure.ac (or configure.in), the results of most tests are already saved in ac_xxx or am_xxx variables. Some more complex results shall be saved in some shell variables. This way, it's enough to add some sh code just after the AC_OUTPUT macro to print the content of these variables. If people from Clamav accept the idea, I can submit a patch (configure.in) to do this - or at least a beginning of what I'm thinking about - up to you to complete with all you may want to display in the summary. But ok, either way if you consider this isn't something interesting, I respect your opinion. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
