Nathan Brink wrote: >> > I don't think it is a good idea to add extra summary code to > ./configure. I don't like it when other programs do this because it > departs from the normal output of ./configure scripts. Maybe if a > configure option --enable-all or --with-all was added, the configure > script could die immediately after a test fails and a certain part of > clamav is disabled. Then the user could add --disable-feature or > --without-package until all tests passed - then he'd know exactly what > his clamav can/can't do.
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. But OK, I agree that all this is a "question of colors and tastes" 8-) _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
