Re: rtag/taginfo/posttag script to send one email

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jim Searle <address@hidden> writes:

> I've written scripts for taginfo & posttag triggers. The taginfo script
> writes the last seen directory/file to a temporary file, and the posttag
> script keeps gathering up file information until the last directory/file is
> seen.   These scripts are similar to the commmitinfo & loginfo scripts other
> use, which are commonly called commitcheck and log_accum.
> 
> The taginfo/posttag scripts work perfectly for the 'cvs tag' command.  But
> now I find the behavior of the 'cvs rtag' command is different.  For example
> if you run:
> - cvs tag dir/a dir/b dir2/c
> This will call the following:
>  - taginfo dir/a dir/b
>  - taginfo dir2/c
>  - posttag dir/a dir/b
>  - posttag dir2/c
> 
> So this works as I expected.  Since taginfo is called on all files before
> posttag is called, the posttag is able to know when it hits the last file so
> it can send the email.
> 
> But, when you run:
> - cvs rtag dir/a dir/b dir2/c
> It will call the following:
>  - taginfo dir/a
>  - posttag dir/a
>  - taginfo dir/b
>  - posttag dir/b
>  - taginfo dir2/c
>  - posttag dir2/c
> 
> So there is not elegant way for posttag to know when it's at the last
> file....

True.

> Does anyone know a good way to handle this so when someone says 'cvs rtag
> dir/a dir/b dir2/c' only one email is sent out immediately after the final
> tag operation?

The best suggestion I could give you would be to modify the src/rtag.c
file to introduct a new postrtag trigger.

If you do it, feel free to send a copy of it to the address@hidden
mailing list. The patch would best be in 'unified' format and include
tests for sanity.sh and the documentation.

        Good luck,
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFDa/RqCg7APGsDnFERAvRYAKDKKfZunHi72Vas00a3NqGLTWR7GwCgglmw
nlpQnDDHs2oaFYpdjQ3uEGc=
=SCBF
-----END PGP SIGNATURE-----