...
 BJ> You will need to get in the habbit of running make 
 BJ> clean followed by a
 BJ> make build after making updates to CVS to test that we didn't break
 BJ> anything.....

 BS> It wouldn't help because it was a missing include file 
 BS> in the CVS repostery.. I need to do a CVS checkout on 
 BS> another dir, to check that I corrected all the errors.. 
 BS> But sourceforge is a problem, because the correctings 
 BS> is getting on 24 hours later :(

Ah....  Sometimes when I'm making this type of update, I'll download from
sourceforge into a clean directory and attempt a recompile to check for
this type of thing....  Yes, that takes added time.....

 BJ> I know, sometimes that isn't convientent that something
 BJ> broke at that point in time, but we need to get in the habbit.....
 BJ> And yes, we'll still miss things at times.....

 BS> Let's hope sourceforge is getting better!

I suspect they will keep development seperated from regular users due to
bandwidth issues......  Now, they might get the frequence of updating the
backup servers (that regular users access) increased.....  At one point I
saw something saying they wanted to increase from once a day to four times
a day (every six hours instead of the original 24 hour update).....

Take care.

Bob Jones, 1:343/41



--- Maximus/2 3.01