Hello, > I was considering using CVS for that at one point, but the way CVS > distributes its metadata and recurses makes that insane. For git, it > would be trivial. I have a shared environment, and handle it this way: - I edit all files on my machine on university or at least put it there per scp when I am done modifing them local. - I have file called .env in my home which contains a list with all files I want to 'distribute'. - There is a script called envup, which updates all files which are not up2date. It uses perl because perl is everywhere I have an account on. After that I call a perl preprocessor to generate ssh config files (there are floating so much ssh versions out there) and one to adopt my .screenrc (for the machine local screen) to my needs. my .bash_profile does a lot of testing to add paths and sets aliases based on the environment of the machine and not based on host/domain names. Files with lot of deltas like my .fvwm2rc or .bash_profile are all version controled using rcs on a per file basis of course. This works very well for me on Linux, Solaris, OpenBSD, FreeBSD, NetBSD, OSF, AIX, MacOSX, name it ... Oh and to bootstrap my environment on a 'new' machine: tar cfz env.tgz `cat .env`, move it over, unpack and re login. A while ago I also distributed binaries (bash, rar, fvwm) via envup for my environment, but I adopted now to something that works everywhere, and if it doesn't I do that manual. So envup only transfers stuff which is new. (I have some accounts on low bandwidth sites). One known side effect. If envup doesn't find md5sum binary it just transfers all files. Oh and a friend and colleague has a similliar script only that he pushes his environment out. Thomas - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2.1.8 : 2005-05-25 07:41:58 EST