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.
Are you not able to use an automated build system to produce the executables and hence be sure they have been built from the correct set of checked-in sources ? Or even if the build is not automated, then to have a procedure whereby someone checking in sources is required then to set the tag and update or export by tag to perform the build to produce the executable ? This would mean you could be sure the executable was produced from the associated sources. The executable can then be given a matching tag. Regards, Richard. -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Kenneth Sørensen Sent: 15 December 2005 14:09 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: VS: [cvsnt] commit missing file Hi Bo I am aware that tags should be used to keep consistency between files. We also do that but the consistency is not kept when CVSNT does not commit what we expect it to do. The problem is that the compiled code is deleted or renamed instead of being replaced with new code. When we do a commit for the module it is intended that both source code and the compiled code should be committed. Instead only the source code is committed. Next we tag the module and now the tag is assigned to the new revision of the source code but the old revision of the compiled code. The result is that the old revision of the compiled code is tagged with two different versions. All this could be avoided if we could make CVSNT check that all files are present when it commits. Of course we could make a script that performs the checks. However, this is a bit time consuming compared to just click commit in WinCVS. I hope this explains why I ask this question. /Kenneth -----Oprindelig meddelelse----- Fra: Bo Berglund [mailto:Bo.Berglund at system3r.se] Sendt: 15. december 2005 13:01 Til: Kenneth Sørensen; cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Emne: RE: [cvsnt] commit missing file Consistency between files is not obtained by simultaneous commits in CVS. It is obtained by tagging the files that belong together with a common tag value. /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Kenneth Sørensen Sent: den 15 december 2005 12:35 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] commit missing file Hi I wonder if this is the intended behavior of CVSNT? I checkout a module containing some files. Then I delete (not cvs remove) one of the files and change another one. Then I do a commit on the module to store my changes. Now I wonder - CVSNT does not complain about the missing file even if I write the command: "cvs commit <missing-file>" it will not complain or warn. In the later nothing happens. Often this will not be a problem. However, we store our compiled code in the repository together with the source. If the compiled code is deleted or missing due to some error it will not be committed together with the source code and we loose consistency between source and compiled code. Is this behavior intended and is there a way to make sure that this will not happen? We use CVSNT ver. 2.0.58d on Windows 2000 on server and client. /Kenneth _______________________________________________ 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 _______________________________________________ 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