Re: Ignoring files known to CVS, when updating

[Spiro Trikaliotis]

Hello Marc-André,

* On Tue, May 08, 2007 at 03:14:59PM -0400 Marc-André Boucher wrote:

> Is there a way to ignore files that are already known to CVS?

Not really ignoring, but you can make sure CVS will not try to update
them (and refuse to check them in).

Just create a "sticky tag" on them. This tag has to point to a specific
revision (that is, no branch).

Take, for example, you want to make sure that "Doxyfile" is not updates.
Use "cvs status":

$ cvs status Doxyfile
===================================================================
File: Doxyfile          Status: Up-to-date

   Working revision:    1.11
   Repository revision: 1.11    /var/lib/cvs/testproject/Doxyfile,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

Ok, so, we have revision 1.11. Now, check out exactly that version:

$ cvs update -r 1.11 Doxyfile

Now, you have a "Sticky tag" on the file:

$ cvs status Doxyfile
===================================================================
File: Doxyfile          Status: Up-to-date

   Working revision:    1.11
   Repository revision: 1.11    /var/lib/cvs/testproject/Doxyfile,v
   Sticky Tag:          1.11
   Sticky Date:         (none)
   Sticky Options:      (none) 

Now, even if you update, CVS will try to update Doxyfile against
revision 1.11. As that revision newer changes, the file will never be
updated.

Note that VICE will also refuse to check in the changes, as 1.11 is a
specific revision. VICE has no possiblity to know "were" (at what
revision) to check the changes in.

If you want to update the file against the latest version, just use -A
on update:

$ cvs update -A Doxyfile

This removed the sticky tag from the file, and updates it to the latest
revision.


Note that you have to do these steps for every file. Well, if you want
to update all files, you can use "cvs up -A" (without specifying a
file), and CVS will handle all files in all directories recursively.

Also, note that you must determine the revision number for any file
separately. Fortunately, the process can be automated with some bash
script rather easy.

HTH,
   Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/