[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tue, 16 Sep 2003 18:01:45 +0200
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
I want to use cvs for a directory that contains scripts. I don't want
everyone to change the scripts in the directory: I won't have
accountability. Thus, it is under cvs. People should check out,
change, and submit. I don't want them to write to the directory itself,
because they will forget to check in.
I would like changes to propagate to the script directory immediately.
Everytime someone commits, an update would be executed in the script
directory. Is that possible?
I have tried a loginfo script, but there is a problem with the locks:
the cvs update runs when the commit has not released the lock yet.
I have looked on the web and found some references, but nothing very
satisfactory. I have seen ACU, but it seems more concerned with
managing multiple machines (which is not a problem), than with the
lock. I have also thought about putting a pause into the script that
does the update, but that does not seem very safe, not do I know how to
do it. (My shell programming is bad, and I don't know how to spawn a
process from loginfo.)
Is there a good solution for this? Should I consider a different setup?
- automatic checkout,
Roderick Bloem <=