On Oct 24, 2004, at 3:29 PM, Mark Adams wrote:
Matt wrote:
What's the worst that can happen? It fails to compile, and you still needThe worst that can happen? I descend once again into dependency hell and spend hours loosing my mind over this. I totally alienate my sense of well being and take up arms on a shooting spree that threatens everyone in a 400 mile circle leaving my children without any parents.
to find a packaged version. You'll be no worse off than you are now.
Fortunatley, that didn't happen. I snagged a copy of source and it compiled smoothly. It seems to be working just fine for now.
Stupid question (I've got TONS of them :-) ...
When you only install programs from source, how do you know when upgrading them that there aren't remnants of binaries or libraries scattered around the OS?
My process for installing a new version: Preserve the previous build for fall-back purposes
1. dl the source for the version of interst 2. read the dox for build changes 3. run a configure/make script (for repeatability - has my chosen options in it) 4. examine the new conf files for interesting entries 5. make backup copies of conf files from previous version 6. stop clamav procs 7. rm -f /usr/local/lib/*clam* (to remove old libraries) 8. make install 9. check again conf files - adjust as needed for new version 10. restart clamav processes
If you run make -n install you will be shown what make would do in an install and where things will be put. This will tell you what you need to remove.
dp _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
