Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
First of all: It is of course possible to arrange custom software that can do almost whatever you like with anything.... But there are a couple of things you need to know: 1) It is *not* possible with CVS to have two servers with the same files and keep them in sync when users are allowed to commit to both. The way CVS keeps track of the revision history makes this impossible. 2) You can always keep a second CVS server as a READ-ONLY mirror of the live server. This is for example what is done at SourceForge. People with commit permissions use the "real" server whereas interested viewers can get the sources from the public mirrors after a certain sync time delay. 3) Your idea seems to me like one where you want one server to ONLY hold release code and nothing else. So it looks like two separate servers to me. And since the second only shall hold release code then there will be a big limitation as to who can commit stuff there. In principle the release server will be a readonly mirror except to the Admin... What I think you could do is the following: - Consider the RELEASE server as a ReadOnly server for all but the Admin - Develop on the DEVEL server until your are ready for release - Let the Admin cvs export the tested release code base from DEVEL - Then let him cvs import the release files to RELEASE while setting proper module name and branch and release tags I think that cvs import was designed for a purpose that is not quite the same as yours but very similar so the "engine" should be usable for it. The sandbox concept is not as good because there will be a lot of manual handling of added and removed files. This is automatically taken care of by the cvs import command. /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Gerhard Fiedler Sent: den 30 maj 2005 13:48 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Re: Sync of Local and Remote CVS Server Manjunath N.S. wrote: > Can you please give information about the how to Synchronization of Local > and Remote CVS server. Requirement is like once code is compilable on > Local CVS Server, it is added to Remote CVS and any updates like newly > added files and new updates in Remote CVS should be reflected and auto > Merge of files I want to avoid with the Local CVS. I've heard of tools for repository synchronization, but I don't know them and I'm not sure that's really what you want. You could do the following. You have two sandboxes, one of the local server and one of the remote server. You develop in the sandbox of the local server. Once that code is good, you copy it into the sandbox of the remote server, add/remove any files that are new or are not needed anymore, and commit. (This of course could also be done with branches in one repository.) Not sure this is what you were looking for... Gerhard _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs