[cvsnt] metadata in CVS

[Aditya Gandhi]

Hi Keith,
Thanks a lot for your inputs on both my mails
Just a clarification on the metadata front...
Actually the requirement is to get a version history (log) of all the
files that are of a particular type (PLAN). Further the version history
should be about all activity that happens on these PLAN files after a
baseline (or say between two baselines).
Say for example I have there PLAN docs in my project. All have been
tagged to be of type 'PLAN'. At end of design I update the plan for
implementation and then baseline it (which in itself is a tag). Then I
need to track all the changes (version history) of all these plan docs
after the baseline.
Therefore, just using the cvs log -SN -rPLAN <module name> will not work
here.
Will get back to you and the group if I need some help on ViewCVS.
Once again thanks for your comments
- Aditya Gandhi

  -----Original Message-----
  From: keith d. zimmerman [mailto:lists at kdz13.net]
  Sent: Tuesday, February 03, 2004 10:07 PM
  To: Aditya Gandhi
  Cc: cvsnt at cvsnt.org
  Subject: Re: [cvsnt] metadata in CVS
  
  Hi again Aditya,
  
  again, comments inline...
  
  Aditya Gandhi wrote:
  
  > Hi all,
  > Looking for some thoughts on tagging some docs a certain way....
  >
  > I am planning to use CVS as code and doc repository and have a need
to
  > be able to have some metadata for files based on which I need to
create
  > some reports.
  >
  > Ex.- Plan could be a type of a document and I might need to query my
  > repository to find all plan documents and get a history of all
changes
  > that have happened to all such files since a baseline.
  >
  > What options do I have to do such a thing....
  
  One option would be using the viewcvs commit database I mentioned in
my
  previous e-mail
  
  >
  > Here are some of my thoughts...  Would appreciate if people can
comment
  > on this or any other alternatives that come to their mind
  >
  > Can I tag all such documents with a tag say 'PLAN' and then use a
cvs
  > command to do the above. If so what will such a command look like?
  
  
  >
  > I know one option could be creating a macro in WinCVS which does
  > something like this
  > 1. cvs log -S -R rPLAN <module name> to get names of the all files
that
  > had been tagged using PLAN
  > 2. Process and use this list as input to a new command -> cvs log
<file
  > names>
  > Some of the problems that I can foresee with this
  > 1. If the number of files is huge then one might end up hitting the
CVS
  > (?WinCVS)limit for the number of chars that can go in for file names
  > (~32000 char)
  can't you simply do this with a single command?  IE:
  	cvs log -SN -rPLAN <module name>
  
  > 2. Once tagged as PLAN a document can not be untagged (Is that
true...
  > how can one remove a particular tag from a doc?)
  cvs tag -d PLAN filename, filename,...
  
  -kz