Date: Fri, 21 Nov 1997 01:26:37 +0000 From: Brian Somers <brian@awfulhak.org> To: Nate Williams <nate@mt.sri.com> Cc: Mike Smith <mike@smith.net.au>, chad@dcfinc.com, rkw@dataplex.net, brian@awfulhak.org, andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org Subject: Re: Version Resolution? Message-ID: <199711210126.BAA26136@awfulhak.demon.co.uk> In-Reply-To: Your message of "Thu, 20 Nov 1997 16:21:17 MST." <199711202321.QAA11798@mt.sri.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Where is this 'counter' stored? It's got to be in one place so that all
> > > of the different distribution mechanisms get the same information if
> > > they grab the same file (CTM/CVS/CVSup). If not in one place, then all
> > > of the distribution mechanism must generate the *EXACT* same information
> > > given the *EXACT* same information, and given that the propogation
> > > delays of the sources throughout the world, then simple timestamps won't
> > > work.
> > >
> > > So, how do you do it?
> >
> > It has to be done by CVS; each commit increments a counter. This means
> > that simultaneous commits become impossible, as the object containing
> > the counter has to be locked as part of the commit.
>
> This file then increases w/out bounds, which is unacceptable.
Hmm, CVS without the revision history ;-) How about simply creating
a cron job that *overrites* the ,v file with a fresh one. cvsup &
ctm et al should be happy. If we only do it once a day, it should
work.
> Nate
--
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <bri@OpenBSD.org>
<http://www.Awfulhak.org>;
Don't _EVER_ lose your sense of humour....
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711210126.BAA26136>