Mike Sutton wrote:
> On 12/04/00 14:55:21, Youngman, James wrote:
> > > > I would ideally like also to be able to restict how tags can be used
> > > > (e.g. tags of a certain format can be used only in a certain way -- in
> > > > my case, only on the top-level module and not directly on the modules
> > > > it includes).
> > > Restricting and verifing tags is what the purpose of taginfo is. So
> > > you second argument contridicts your first. taginfo can verify your
> > > tags and log them.
> > From the description of taginfo in the manual it would appear that you get a
> > separate invocation of the script for each recursed subdirectory. Hence
> > taginfo can't enforce the "only on the top-level module" constraint I
> > mentioned above, as far as I can tell.
> Sure you can. taginfo gets the full repository directory. When the
> top directory is processed it can save a tempfile that the subsequent
> calls look for. Look at the log_accum script that comes with CVS.
>
> What is really missing is a post tag trigger.
Or see my cvssupport project at sourceforge
(https://sourceforge.net/projects/cvssupport). If you write cvssupport
plugins instead of regular cvs plugins, you can control this behavior
explicitly. The project is best accessed via (surprise) CVS at this
stage; I'm still working on polishing the installation process.
Cheers,
Laird
--
W: [EMAIL PROTECTED] / P: [EMAIL PROTECTED]
http://www.amherst.edu/~ljnelson/
Good, cheap, fast: pick two.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
