Török Edwin wrote: > On 2009-03-01 23:32, Jose-Marcio Martins da Cruz wrote: >> Some examples about clamav : >> >> * Solaris don't have ncurses library - so, clamdtop won't be built. This >> isn't critical. But it's interesting to know that clamdtop won't be >> built and the library wasn't found. And configure shall not stop if >> ncurses wasn't found. >> >> * Summarizing all buggy libraries (libz, ...). >> >> * It's usually simple to dig a summary of things which weren't Ok, than >> reading all config.log files. I know very few people who dig config.log >> files. > > 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. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
