begin quoting [EMAIL PROTECTED] as of Fri, Sep 22, 2006 at 04:44:50PM -0700: > On Fri, Sep 22, 2006 at 02:52:06PM -0700, Stewart Stremler wrote: > > > Any advice how to manage this complexity? > > > > Put it all under version-control. > > Yes version control seems like the logical thing to do.
Or rsync to a common machine, if you don't care about history. > This has problems too however... > > 1. What if one of your machines is not on the open net? Put the repository on a thumbdrive. Or manually sync it up using a CD or thumbdrive or floppy. > 2. You must be religious about checking in all changes on every > machine to *propagate* changes. On logout, warn if there are changes that haven't been checked in. > 3. You must be religious about updating your checkout directory > on all machines to *get* changes. On login, warn if there are changes in the repository that haven't been updated. > 4. Your repository will grow huge after a while if your $HOME changes > a lot. Not so much. At least, not if you only check in configuration files. Surely you can spare a gigabyte of disk (or flash) for the repository. > I suppose these issues can be surmounted with an SSH based Subversion > server and crontab scripts.... Or login/logout scripts. You can also use distributed repository tools (arch, darcs, etc.) and keep a local repository on each machine; but you'll have to talk to Andrew about how to make the repositories link up properly with each other. -- _ |\_ \| -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
