RE: tag doesn't always tag

[Jacob Weber]

I'm writing a script to compare the current state of a directory against a previous state (which was tagged). Sometimes that previous state will have been empty. If so, I don't want the script to fail. It should still show me the files that have changed since that tag, which in this case will be all of the files.

 

This works if I manually add my tag to the val-tags file before tagging, which seems like a clumsy approach. But I would rather not have my script start arbitrarily creating dummy files.

 

All the CVS commands seem to go nuts when you try to compare or tag an empty directory. I understand that CVS dosn't know anything about directories, but it seems like the behaviour should at least be consistent. It makes it very frustrating to automate.

Jacob

 

-----Original Message-----
From: Andrew Goktepe [mailto:address@hidden
Sent: Wednesday, October 26, 2005 11:48 AM
To: Jacob Weber
Cc: address@hidden
Subject: Re: tag doesn't always tag

Why do you need to remember an empty directory?

 

Based on my experience, you either need to put a dummy (maybe a readme) file in the directory so that is no longer empty, or you need to have your build process create the directory at runtime.

 

-Andrew
 

On 10/26/05, Jacob Weber <address@hidden> wrote:

Here's a sort-of simple problem. If I do "cvs tag" on an empty directory, it
looks like CVS doesn't add anything to the CVSROOT/val-tags file, and thus
has no idea that the tag ever existed.

So say I'm trying to remember the state of a directory, which happens to be
empty, so I can restore it later. When I try to restore it. CVS won't find
the tag, and it won't do anything. It should restore an empty directory.

Is this a bug? Is there a way to force it to add the tag to the val-tags
file?
Jacob





_______________________________________________
Info-cvs mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/info-cvs