On Tue, 4 Apr 2006, Igor Peshansky wrote:
> Earlier, I wrote (regarding firing off the build once some number of files
> have changed):
>
> > FWIW, a slightly better way of structuring your make is to remember the
> > date/time of the last make (as a timestamp on a file, perhaps), and
> > simply compare CVS as of that date/time with the HEAD. If the HEAD has
> > certain properties (some particular files changed, the number of changed
> > files is greater than some threshold, etc), then fire off a checkout and
> > the build.
>
> On Tue, 4 Apr 2006, Richard Quadling wrote:
>
> > Thanks for that. I'd not thought of using the CVS itself.
> > Living and learning.
>
> It would be nice to quote at least some relevant part of the message
> you're replying to, just to set the context for people seeing this thread
> for the first time.
>
> Also, a small clarification: when I said "compare CVS as of that
> date/time", I did not mean the repository itself, but the "cvs" command.
^
output of the appropriate
Sorry, that's what I get for firing off emails in a hurry.
> In your case, if you only do the checkout whenever you do the make, using
> "cvs -n checkout" should suffice -- just examine the output of that.
> E.g., something like (untested):
>
> cvs -qn checkout > log && \
> [ `wc -l log` -ge 50 -o `grep -F -c -f IMPORTANT_FILES log` -gt 0 ] && \
> cvs -q checkout && make
>
> where IMPORTANT_FILES is a file that contains the list of files changes to
> which should kick off the build no matter what, one per line, with a 'U '
> in front of it (to simulate cvs output).
> Igor
HTH,
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
