Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <39931E6A.77F187AD@ece.gatech.edu>
Date: Thu, 10 Aug 2000 17:28:10 -0400
From: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: gdbm & cvs packages ready for official inclusion?
References: <20000810141348 DOT A4458 AT cygnus DOT com> <1999 DOT 000810 AT logos-m DOT ru>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Egor Duda wrote:
> 
> CF> I looked at the sources and it looks like whomever wrote readdir made
> CF> some false assumptions about the values of errno.  It looks like it will
> CF> always set errno when there are no more files.  I'm testing a fix for
> CF> this now.
> 
> this  bug  had been fixed in development version of cvs some time ago.
> instructions foe getting current sources of cvs can be found on
> http://www.cvshome.org/dev/index.html#current
> 
> i'm intensively using it for almost half a year without any problems.
> 

You've been using a version of CVS compiled from their development
release which was current as of six months ago, or you continually
update your local cvs.exe to track their sources daily?

You certainly cannot have been using today's development version (e.g
'checked out from their repository') for the last six months. That's the
problem with development versions -- they have NO history. 

Technically, cvs 1.10.8 *is* an experimental release -- only 1.10.0 is
an official release. But at least the source to 1.10.8 has been stable
for some time.

Since I hadn't been tracking the CVS development, I figured it would be
best to stick with a relatively 'stable' checkpoint, rather than
slurping up the latest, greatest, and buggiest and inflicting it on
cygwin users. The cvshome webpage you reference says:

> The current working version of CVS is available to all. It may 
> not be thoroughly tested and it may not even compile on your 
> system. So, unless you are helping to develop CVS or love 
> getting the latest, greatest, and buggiest, there is a good 
> chance that you should be running a released version of CVS 
> instead.

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com