-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [EMAIL PROTECTED] wrote: > 1. What if one of your machines is not on the open net?
I have my svn server accessible from the open net. If one of the clients is behind NAT it is no problem. If it has no net connection at all then you really have few choices. > 2. You must be religious about checking in all changes on every > machine to *propagate* changes. This is why I use my script check4change.sh which does an svn stat whenever I do an ls on a dir and reminds me to check in changes by changing the prompt string. > 3. You must be religious about updating your checkout directory > on all machines to *get* changes. I include in my .bashrc a backgrounded svn update command so it gets updated when I log in. But sometimes this may be undesirable. > 4. Your repository will grow huge after a while if your $HOME changes > a lot. Doubtful. How much are you really going to type into your dotfiles? > I suppose these issues can be surmounted with an SSH based Subversion > server and crontab scripts.... svn+ssh works well. I don't have any crontab scripts although that would be another way to update everything and possibly better than doing it on login. - -- Tracy R Reed http://ultraviolet.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFFJgO9PIYKZYVAq0RAjfOAKCWknF6cW6njRfGGmAhdcxTQgp5ZgCfXz1n dFngBU3rne7mvErUw2vZSi4= =9YAB -----END PGP SIGNATURE----- -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
