[cvsnt] Re: how to get the branch information before

[cvssteve at diablo-technologies.com]

I've noticed this issue recently too.

I'm trying to restrict both the filenames and the branch and non-branch tags
used in different cvs modules.

There follows a list of some of the major checks I'd like to enforce, along
with the behaviour I've noticed.

>From the CVS Server I'd like to precheck the following:

a) The directory name used prior to altering the cvs repository 
   when that directory is added 
   Note: "cvs add <dir>" immediately modifies the repository 
         (i.e. doesn't require a commit). Also aborting 
         "cvs add <dir>" in precommand still leaves a CVS 
         directory behind in the client side called "<dir>/CVS"

b) The file and branch name used for each file before it is commited.
   Note: commitinfo and precommand do not provide this info 
         (as Bo described below).

c) The Tags that are applied to specific cvs modules and 
   abort when appropriate
   Note: taginfo has been completely dropped from the CVSNT manual
         although it still works.

I've filed bug reports on most of the above, but I thought I'd capture it
all in one place.

Regards,

Steve


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of
Bo Berglund
Sent: November 5, 2005 12:24 PM
To: cvsnt at cvsnt.org
Subject: [cvsnt] Re: how to get the branch information before

On Sat, 05 Nov 2005 16:33:39 +0100, Bo Berglund
<bo.berglund at telia.com> wrote:

>
>Yes, you can get all the info you need by adding command line argument
>to your call to the Project.exe file (by the way you should only use
>forward slashes inside the CVS script files, \ is treated as an escape
>character).
>Look in the helpfile for CVSNT under the section "Reference manual for
>Adminstrative files", specifically at the chapter "The commit support
>files".
>Here you can see which command arguments you can use to get almost all
>the info you need to cope with the problem at hand.
>

After creating a command line argument checking program and running
that from the commitinfo script I see that I cannot really extract the
tag (branch tag) of the files being submitted for commit. :-(

Tony,
is there a way to get this info from the commitinfo file using the new
triggers and the common syntax or wahtever?

I used this construct:
ALL C:/somepath/CheckArguments.exe %s %m %p %d %h %u %r %R %S %e %H %P
%i
And the output was:
20051105 18:18:18 Param1: BranchAddFile.txt
20051105 18:18:18 Param2: Checking commitinfo arguments list
20051105 18:18:18 Param3: ModuleXX
20051105 18:18:18 Param4: Sat Nov  5 17:18:16 2005
20051105 18:18:18 Param5: polaris.agiusa.se
20051105 18:18:18 Param6: Bosse
20051105 18:18:18 Param7: /KORVkiosk
20051105 18:18:18 Param8: C:/DATA/CVSREPO/Bosse
20051105 18:18:18 Param9: 1500436ce9585fe3
20051105 18:18:18 Param10: notepad
20051105 18:18:18 Param11: POLARIS
20051105 18:18:18 Param12: C:\Programs\cvsnt\Temp\cvs-serv5376
20051105 18:18:18 Param13: CVSNT 2.5.01 (Travis) Build 1976 (cvsgui
active)



/Bo
(Bo Berglund, developer in Sweden)