[cvsnt] script that runs when a module is checked out??

Alexandre Augusto Drummond Barroso adrummond at bdmg.mg.gov.br
Thu Jan 2 19:51:57 GMT 2003


Sorry, I didn't expressed myself clearly. What I really meant is 
that I need a configuration file for running a script every time a
checkout occours instead of editing modules file and adding:
module_name -o script_for_maintnance_of_checkout_log $USER

[]s

Xandao.

-----Original Message-----
From: Bo Berglund [mailto:bo.berglund at telia.com]
Sent: Thursday, January 02, 2003 3:25 PM
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] script that runs when a module is checked out??


On Thu, 2 Jan 2003 16:15:50 -0300, "Alexandre Augusto Drummond
Barroso" <adrummond at bdmg.mg.gov.br> wrote:

>I have the same needs... Unfortunately I have to add a line with 
>-o option in modules configuration file every time a new module is 
>created. It would be great if there were a way to add a default (I 
>mean a DEFAULT statement like other configuration files) for -o 
>option in modules conf file.
>

This is not really what I meant...
What you are looking for is a way to autometa the management of the
modules file so that newly added modules get an entry in the modules
file. This can probably be done through the commitinfo or loginfo
scripts.

But I would like to know *which users* have checked out which
modules/files. So I thought that if I had a script similar to loginfo
(which works on file commits), but is triggered on a cvs checkout
command I could fix a program that logs this information somewhere
where it can be later retrieved:
Date, UserID, Module (or Module/File)



/Bo
(Bo Berglund, developer in Sweden)
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt





More information about the cvsnt mailing list