head	1.3;
access;
symbols;
locks; strict;
comment	@# @;


1.3
date	2001.06.05.01.37.54;	author stack;	state Exp;
branches;
next	1.2;

1.2
date	2001.06.04.16.26.47;	author stack;	state Exp;
branches;
next	1.1;

1.1
date	2001.05.10.20.40.42;	author thom;	state Exp;
branches;
next	;


desc
@@


1.3
log
@Backing out my adding of the '-C' flag to cvs update in loginfo.  It doesn't
work inside loginfo.  Inside loginfo, a patch is applied to the file on
disk. If file on disk has been locally modified or is not the immediate
ancestor, the patch will often fail -- there will be merge errors.  Outside
of loginfo, the locally-modified file is moved aside if there will be
conflicts merging; then the file is updated.

Spent a while trying to figure why the difference.  Local vs. remote
repository is the only obvious difference.  Backing out change for not so
doesn't interfere w/ rolling of T106.
@
text
@#!/usr/bin/env perl

# place a line in the loginfo file like
# ALL $CVSROOT/CVSROOT/publish.pl %s
#

# Tigris Root
my $SANDBOX = "__SANDBOX__";

# publication directory
my $HTDOC = "$SANDBOX/data/helm/htdoc";

my $CVSBIN = '/usr/bin';
$PATH      = "$PATH:/bin:/usr/bin";

my ($dir, @@files) = split(' ', $ARGV[0]);

#
# if if this directory is published.
#
if ( -d "$HTDOC/$dir" ) {
  FORK: {
      if ($pid = fork) {
          ## in parent
          ## do nothing
          exit 0;
      }
      elsif ($pid == 0) {
          sleep 5;
          chdir "$HTDOC/$dir";
          exec "$CVSBIN/cvs", "-Q", "update", "-d";
      }
      elsif ($! == EAGAIN) {
          sleep 2;
          redo FORK;
      }
      else {
          die "Can't fork: $!\n";
      }
  }
}

exit 0;


@


1.2
log
@Change the cvs updating of web content so it does 'cvs update -Cd'
rather than 'cvs update -d' (The -C says, do fresh checkout; ignore
what is on the filesystem already; do not try to merge).
@
text
@d31 1
a31 1
          exec "$CVSBIN/cvs", "-Q", "update", "-Cd";
@


1.1
log
@change the web publishing process to so that only one line is needed in
the loginfo file, "ALL $CVSROOT/CVSROOT/publish.pl %s", this line well
check to see if the commit contains published content and if so publish
it.
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d31 1
a31 1
          exec "$CVSBIN/cvs", "-Q", "update", "-d";
@

