Larry Jones wrote:
>Branch names *are* tags. CVS uses it to validate that a user-entered
>tag is valid: If the tag appears in the val-tags file, it is assumed to
>be valid. If the tag does not appear in the val-tags file, then CVS
>goes looking through all of the files in the repository that are
>specified in the command. If one of them contains the tag, it is valid
>and is added to the val-tags file. If it is not found, the user is
>given an error message.
I have a related question.
How can you prevent an error if a read-only user wants to check out a
tag that no one has checked out before?
Here's how I encountered the problem:
I have a script that exports and installs a module. For security
reasons, it runs as a read-only user. If I make a new branch tag and
then run the script, this is what happens:
my script says:
cvs -d [readonlyuser@repository] export -r [new-tag] [module]
cvs says:
cvs [export aborted]: cannot write
/usr/local/cvsroot/CVSROOT/val-tags: Permission denied
If I do this as a user with write access:
cvs export -r [new-tag] [module]
I can then run the script with no errors.
What's the best way to fix this problem?
Thanks.
Mike Ciul
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
