Gary L Burnore wrote: > > > Gary L. Burnore > gburn...@databasix.com > > > >> -----Original Message----- >> From: clamav-users-boun...@lists.clamav.net >> [mailto:clamav-users-boun...@lists.clamav.net] On Behalf Of >> Jose-Marcio Martins da Cruz >> Sent: Sunday, March 01, 2009 4:33 PM >> To: ClamAV users ML >> Subject: Re: [Clamav-users] Two suggestions >> >> 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. > > "Solaris doesn't" not "Solaris don't".
He's a South American living in France - English is two steps removed from his first language. > > > However, www.sunfreeware.com has ncurses 5.6 in pkg form > which is usually installed for other reasons anyway. And it is easily built from source as well, 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. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
