Hi there, On Sun, 16 Sep 2007 Stephen Gran wrote:
> The simplest approach to making the work would be to dedicate a > directory to keeping the source lying around, and then keep a file > somewhere outside of that source tree with the ./configure flags. > That way, you can easily uninstall or rerun the build with the same > flags. That's exactly right, and it's just what I've been doing for the past decade or so that I've been using Linux. It's sooooooo useful to be able to go to one place to find out what you have to do when you last upgraded that sendmail milter/ssl library/apache module... Package managers are fine if you package things yourself, but if you rely on others to produce the packages then it's only a matter of time until someone packages something in a way which doesn't fit well with something that you're already doing. I've rarely used one for more than a couple of weeks before that's happened. Sure, it's a nuisance to have to document what you've done. But if this was easy, anybody could do it. :) -- 73, Ged. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
