> So, what do you think about putting one standard installation under > bzr (Windows) > control and then pulling in changes from the different PC's when they are > ready > for it ?
That seems like a workable approach. A disadvantage is that by putting all of those binaries into bzr, you'd get a large .bzr directory, with all of the previous versions of every binary. However, that would only be true on the master host. On the slave hosts you could use lightweight checkouts and so not take up all of the extra space there for history. A lighter-weight approach would be to use rsync or unison instead, to synchronize the satellite hosts to the master. That would avoid the space and work overhead of keeping the version control history, but you'd lose the ability to roll back changes if for some reason they created problems. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
