Rick wrote: > ... > It's that easy IF you remember that upgrading vpopmail requires upgrading/recompiling > things that use vpopmail.so courier and qmail with the chkuser patch come to mind). > Also, always read the UPGRADE document for the program you are upgrading. > ... > Always read the UPGRADE document if it exists. > ... > > Correct. I guess someone with a wack of free time could write an UPGRADE document > for the toaster but most of us already do read it for the individual packages we > are upgrading. > > Regards, > > Rick >
Rick, thanks a lot for your answer. I'm fully aware that I should ALWAYS read the update instructions of every single package and that not doing so is MY fault. Also I knew that this would be the first answer to my request :-) I guess I could come up with excuses like "I've got to read tons of manuals and docs every day and most of the stuff is either of no interest or doesn't come to the point or I don't understand a single word or ...". As for ClamAV: the update instructions are clearly arranged, explizit but short and easy to understand. So, even my usual excuses wouldn't fit here :-) Bill's qmail toaster IS a great piece of work, no doubt about that, and i really thank Bill and all contributers for their work. When our old qmail system (installed by a guy who left the company) crashed because of a total HD failure, I was able to setup a fresh and far better (!) system with Bill's toaster within 2-3 hours. I just wish that upgrading would be that easy as well, or at least explained in more detail. Not as a substitution for reading the before mentioned upgrade instructions of the packages (see, I've learned my lesson). Besides, reading the ChangeLog of the toaster is one thing, understanding the - maybe implicit - connections between addition/changes of patches and other packages is another. Regards, Guenter
