John Rudd wrote: > Dennis Peterson wrote: > > > My not-so-automated update process looks like this: > > > > > > wget (link to current clamav-XXX.tar.gz) > > > tar xzf clamav-XXX.tar.gz > > > cd clamav-XXX > > > configure --disable-zlib-vcheck > > > make > > > su > > > make install > > > service clamav restart > > > service freshclam restart > > > > > > > You would be wise to uninstall the previous installation so that > > you don't end up with split versions. The man pages have not always > > been consistent nor have library names, and uninstall (make > > uninstall) helps prevent this. > > > > > > It would be nice, though, if there was a "clamav-current.tar.gz" to > download, so that such automated processes could be done more ... > automated.
I don't know that I would want to automate a build script that much. I generally want to be available whenever I install software (source or RPM) just in case something breaks. I've never even bothered to automate the process. ClamAV doesn't update THAT frequently and when it does, the download and build process is very fast even when done manually. Of course, if I had to install it on more than a couple of machines, I might want a script that I could feed the current filename, but I haven't gotten there yet. -- Bowie _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
