[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: automatic checkout

From: Steve deRosier
Subject: Re: automatic checkout
Date: Tue, 16 Sep 2003 10:16:30 -0700
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030428

How about a script on a cron job that periodically (whatever granularity you require from 1 minute to 1 day) checks to see if there's been any new updates and if so does an update to the "production" tree? Seems like a rather clunky work-arround, but it should at least get the results you're looking for.

- Steve

Roderick Bloem wrote:

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?


Roderick Bloem

Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]