On May 23, 2007, at 10:00 AM, Stewart Stremler wrote:
Actually, it's why I tend to prefer centralized version control -- check everything you want to keep (as in, can't rebuild automatically) into version control. If you didn't check it in, you shouldn't mind it getting blasted. That being said, it's often useful to give each developer a "scratch" repository for checking in experiments-in-progress, favorite tools, etc., so if they do sit down on a blank machine, they can easily recreate /their/ preferred environment.
At work, we have one repository for our code and projects, another repository (on a more restricted-access host) for all our configuration management data for cfengine, and I've created my own repository for my scratch space.
Currently we're using subversion, and everything is accessed by the svn+ssh method, which works out pretty well. Creating your own repository is trivial, and I put mine on our main repository server in my home directory with a nightly cronjob to dump it to file for backups, just to be safe (even though I'm using subversion's "FSFS" store, which should mean simple recovery.)
I firmly believe that Lots Of Copies Keep It Safe.My personal (non-work) repository lives on my linux box at home and also gets dumped to file every night. I still have to work out where I'm going to copy _that_ since I don't have any reliable nightly backup set up at home (just weekly copy-to-external-drive-when-I- remember-it, which I'm not putting much faith in.)
Gregory -- Gregory K. Ruiz-Ade <[EMAIL PROTECTED]> OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu
PGP.sig
Description: This is a digitally signed message part
-- KPLUG-List@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
