> DON'T KILL THE LOGS!!!!! Would that they'd be logs. We never had space (or haven't optimized sufficiently) to keep the build logs. Gump's (internal) logs aren't worth a lot, but exist, if wanted. I hope we give good consideration to 'Net history (and access for external services, e.g. google) with Gump3.
> Adam, can you give us (or leo) pointers to where is all the data that > gump saves so that we can restore it on the new installation? Basically there is the MySQL database, and a DBM file (at /usr/local/gump/public/gump/work/stats.db). These contain what history we have. [Same DBM exists for Kaffe, JDK1.5, etc.] BTW: Are we saving the crontab and any scripts in ~gump, Leo? Could be valuable. Where ought we put these to be moved, into Gump SVN? BTW: I hope '/usr/local/gump/packages' is being moved across. That'd remove a huge chunk of the pain of a fresh install. Also, if we kept '/usr/local/gump/staging' (along w/ timestamps) then Gump might continue to accurately records how long since a code update (on more stale projects.) regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
